Integrated server flow-through fixture with state sensor for datacenter cooling systems

ABSTRACT

Systems and methods for cooling a datacenter are disclosed. In at least one embodiment, a server tray or box includes a surface with a flow-through fixture or manifold that extends on both sides of the surface, that includes an inward coupling, an outward coupling, a flow controller, and a state sensor, the state sensor to monitor a flow-through fixture or manifold, where a flow controller of a flow-through fixture or manifold can change a flow of a coolant through a flow-through fixture or manifold and can selectively trap a portion of a coolant within a flow-through fixture or manifold.

FIELD

At least one embodiment pertains to cooling systems, including systemsand methods for operating those cooling systems. In at least oneembodiment, such a cooling system can be utilized in a datacentercontaining one or more racks or computing servers.

BACKGROUND

Datacenter cooling systems use fans to circulate air through servercomponents. Certain supercomputers or other high capacity computers mayuse water or other cooling systems instead of air-cooling systems todraw heat away from the server components or racks of the datacenter toan area external to the datacenter. The cooling systems may include achiller within the datacenter area, which may include area external tothe datacenter itself. Further, the area external to the datacenter mayinclude a cooling tower or other external heat exchanger that receivesheated coolant from the datacenter and that disperses the heat by forcedair or other means to the environment (or an external cooling medium).The cooled coolant is recirculated back into the datacenter. The chillerand the cooling tower together form a chilling facility.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A, 1B illustrate exemplary features of a datacenter coolingsystem subject to improvements described in at least one embodiment;

FIGS. 2A, 2B illustrate exemplary features associated with an integratedserver flow-through fixture or manifold with a state sensor for adatacenter cooling system, according to at least one embodiment;

FIG. 3 illustrates rack-level features associated with an integratedserver flow-through fixture or manifold with a state sensor for adatacenter cooling system, according to at least one embodiment;

FIG. 4 illustrates datacenter-level features associated with anintegrated server flow-through fixture or manifold with a state sensorfor a datacenter cooling system, according to at least one embodiment;

FIG. 5 illustrates a method associated with a datacenter cooling systemof FIGS. 2A-4 , according to at least one embodiment;

FIG. 6A illustrates inference and/or training logic, according to atleast one embodiment;

FIG. 6B illustrates inference and/or training logic, according to atleast one embodiment;

FIG. 7 illustrates training and deployment of a neural network,according to at least one embodiment;

FIG. 8 illustrates an example data center system, according to at leastone embodiment;

FIG. 9 is a block diagram illustrating a computer system, according toat least one embodiment;

FIG. 10 is a block diagram illustrating a computer system, according toat least one embodiment;

FIG. 11 illustrates a computer system, according to at least oneembodiment;

FIG. 12 illustrates a computer system, according to at least oneembodiment;

FIG. 13A illustrates a computer system, according to at least oneembodiment;

FIG. 13B illustrates a computer system, according to at least oneembodiment;

FIG. 13C illustrates a computer system, according to at least oneembodiment;

FIG. 13D illustrates a computer system, according to at least oneembodiment;

FIGS. 13E and 13F illustrate a shared programming model, according to atleast one embodiment;

FIG. 14 illustrates exemplary integrated circuits and associatedgraphics processors, according to at least one embodiment;

FIGS. 15A, 15B illustrate exemplary integrated circuits and associatedgraphics processors, according to at least one embodiment;

FIGS. 16A, 16B illustrate additional exemplary graphics processor logicaccording to at least one embodiment;

FIG. 17 illustrates a computer system, according to at least oneembodiment;

FIG. 18A illustrates a parallel processor, according to at least oneembodiment;

FIG. 18B illustrates a partition unit, according to at least oneembodiment;

FIG. 18C illustrates a processing cluster, according to at least oneembodiment;

FIG. 18D illustrates a graphics multiprocessor, according to at leastone embodiment;

FIG. 19 illustrates a multi-graphics processing unit (GPU) system,according to at least one embodiment;

FIG. 20 illustrates a graphics processor, according to at least oneembodiment;

FIG. 21 is a block diagram illustrating a processor micro-architecturefor a processor, according to at least one embodiment;

FIG. 22 illustrates a deep learning application processor, according toat least one embodiment;

FIG. 23 is a block diagram illustrating an example neuromorphicprocessor, according to at least one embodiment;

FIG. 24 illustrates at least portions of a graphics processor, accordingto one or more embodiments;

FIG. 25 illustrates at least portions of a graphics processor, accordingto one or more embodiments;

FIG. 26 illustrates at least portions of a graphics processor, accordingto one or more embodiments;

FIG. 27 is a block diagram of a graphics processing engine of a graphicsprocessor in accordance with at least one embodiment;

FIG. 28 is a block diagram of at least portions of a graphics processorcore, according to at least one embodiment;

FIGS. 29A, 29B illustrate thread execution logic including an array ofprocessing elements of a graphics processor core according to at leastone embodiment;

FIG. 30 illustrates a parallel processing unit (“PPU”), according to atleast one embodiment;

FIG. 31 illustrates a general processing cluster (“GPC”), according toat least one embodiment;

FIG. 32 illustrates a memory partition unit of a parallel processingunit (“PPU”), according to at least one embodiment;

FIG. 33 illustrates a streaming multi-processor, according to at leastone embodiment.

FIG. 34 is an example data flow diagram for an advanced computingpipeline, in accordance with at least one embodiment;

FIG. 35 is a system diagram for an example system for training,adapting, instantiating and deploying machine learning models in anadvanced computing pipeline, in accordance with at least one embodiment;

FIG. 36A illustrates a data flow diagram for a process to train amachine learning model, in accordance with at least one embodiment; and

FIG. 36B is an example illustration of a client-server architecture toenhance annotation tools with pre-trained annotation models, inaccordance with at least one embodiment.

DETAILED DESCRIPTION

In at least one embodiment, an exemplary datacenter 100 can be utilizedas illustrated in FIG. 1 , which has a cooling system subject toimprovements described herein. In at least one embodiment, numerousspecific details are set forth to provide a thorough understanding, butconcepts herein may be practiced without one or more of these specificdetails. In at least one embodiment, datacenter cooling systems canrespond to sudden high heat requirements caused by changingcomputing-loads in present day computing components. In at least oneembodiment, as these requirements are subject to change or tend to rangefrom a minimum to a maximum of different cooling requirements, theserequirements must be met in an economical manner, using an appropriatecooling system. In at least one embodiment, for moderate to high coolingrequirements, liquid cooling system may be used. In at least oneembodiment, high cooling requirements are economically satisfied bylocalized immersion cooling. In at least one embodiment, these differentcooling requirements also reflect different heat features of adatacenter. In at least one embodiment, heat generated from thesecomponents, servers, and racks are cumulatively referred to as a heatfeature or a cooling requirement as cooling requirement must address aheat feature entirely.

In at least one embodiment, a datacenter liquid cooling system isdisclosed. In at least one embodiment, this datacenter cooling systemaddresses heat features in associated computing or datacenter devices,such as in graphics processing units (GPUs), in switches, in dual inlinememory module (DIMMs), or central processing units (CPUs). In at leastone embodiment, these components may be referred to herein as high heatdensity computing components. Furthermore, in at least one embodiment,an associated computing or datacenter device may be a processing cardhaving one or more GPUs, switches, or CPUs thereon. In at least oneembodiment, each of GPUs, switches, and CPUs may be a heat generatingfeature of a computing device. In at least one embodiment, a GPU, a CPU,or a switch may have one or more cores, and each core may be a heatgenerating feature.

In at least one embodiment, a server tray is disclosed and has aflow-through fixture or a manifold that is an integrated fixture. In atleast one embodiment, such a flow-through fixture or manifold hascouplings, flow controllers, and a state sensor. In at least oneembodiment, this is so a server tray with such a flow-through fixture ormanifold can be used with any coolant in a plug-and-play manner withouthaving to provide additional external features to enable flowadjustments or leak detection depending on a coolant used. In at leastone embodiment, such a server may be coupled to a cooling manifold, suchas a rack cooling manifold on an external side and may be coupled to atleast one cold plate on an internal side.

In at least one embodiment, liquid coolants may be used in servers anddatacenter cooling system, but need monitoring to ensure that itschemical characteristics are maintained. In at least one embodiment,this may be done by taking a sample and sending it to a lab foranalysis. In at least one embodiment, results are then reviewed andcorrective action may be taken. In at least one embodiment, such testingmay be done periodically. In at least one embodiment, a flow-throughfixture or a manifold with a state sensor can address this issue withsuch a state sensor being incorporated for testing of coolants in realtime and directly for a datacenter cooling system so that data can berecorded real time and corrections can be performed in real time.

In at least one embodiment, by taking real time reading forcharacteristics like pH, conductivity, turbidity, infra-red (IR)absorption spectrum, and a general health of a coolant using appropriatestate sensors (or a collection of sensors referred to herein as a statesensor), continuous monitoring and trends may be easier to observe andto address. Such real time testing may be could also result in economiesof scale for large datacenters in comparison to batch monitoring. In atleast one embodiment, such real time aspects enable money-savings fromdegraded cooling performance and system down time, for instance.

In at least one embodiment, a server may include a server coolingmanifold internally that couples between at least one cold plate and aflow-through fixture or manifold. In at least one embodiment, a sensorwithin a flow-through fixture or manifold may be provided in an area ofa flow-through fixture or manifold to enable status information of aflow-through fixture or manifold to be provided to a flow controller ora processor. In at least one embodiment, such information may be to aflow rate, a flow volume, or a chemistry of a coolant to flow through aflow-through fixture or manifold. In at least one embodiment, thisallows a response to address issues of a coolant there through or tonotify of coolant issues. In at least one embodiment, such a sensor is astate sensor that is a self-calibrating sensor. In at least oneembodiment, a self-calibrating sensor can provide calibrated informationpertaining to different coolants used within such a flow-through fixtureor manifold without a need to make adjustments or configurations tosensors for use with certain coolants.

In at least one embodiment, an exemplary datacenter 100 can be utilizedas illustrated in FIG. 1A, which has a cooling system subject toimprovements described herein. In at least one embodiment, a datacenter100 may be one or more rooms 102 having racks 110 and auxiliaryequipment to house one or more servers on one or more server trays. Inat least one embodiment, a datacenter 100 is supported by a coolingtower 104 located external to a datacenter 100. In at least oneembodiment, a cooling tower 104 dissipates heat from within a datacenter100 by acting on a primary cooling loop 106. In at least one embodiment,a cooling distribution unit (CDU) 112 is used between a primary coolingloop 106 and a second or secondary cooling loop 108 to enable extractionof heat from a second or secondary cooling loop 108 to a primary coolingloop 106. In at least one embodiment, a secondary cooling loop 108 canaccess various plumbing into a server tray as required, in an aspect. Inat least one embodiment, loops 106, 108 are illustrated as linedrawings, but a person of ordinary skill would recognize that one ormore plumbing features may be used. In at least one embodiment, flexiblepolyvinyl chloride (PVC) pipes may be used along with associatedplumbing to move fluid along in each provided loop 106; 108. In at leastone embodiment, one or more coolant pumps may be used to maintainpressure differences within coolant loops 106, 108 to enable movement ofcoolant according to temperature sensors in various locations, includingin a room, in one or more racks 110, and/or in server boxes or servertrays within one or more racks 110.

In at least one embodiment, coolant in a primary cooling loop 106 and ina secondary cooling loop 108 may be at least water and an additive. Inat least one embodiment, an additive may be glycol or propylene glycol.In operation, in at least one embodiment, each of a primary and asecondary cooling loops may have their own coolant. In at least oneembodiment, coolant in secondary cooling loops may be proprietary torequirements of components in a server tray or in associated racks 110.In at least one embodiment, a CDU 112 is capable of sophisticatedcontrol of coolants, independently or concurrently, within providedcoolant loops 106, 108. In at least one embodiment, a CDU may be adaptedto control flow rate of coolant so that coolant is appropriatelydistributed to extract heat generated within associated racks 110. In atleast one embodiment, more flexible tubing 114 is provided from asecondary cooling loop 108 to enter each server tray to provide coolantto electrical and/or computing components therein.

In at least one embodiment, tubing 118 that forms part of a secondarycooling loop 108 may be referred to as room manifolds. Separately, in atleast one embodiment, further tubing 116 may extend from row manifoldtubing 118 and may also be part of a secondary cooling loop 108 but maybe referred to as row manifolds. In at least one embodiment, coolanttubing 114 enters racks as part of a secondary cooling loop 108 but maybe referred to as rack cooling manifold within one or more racks. In atleast one embodiment, row manifolds 116 extend to all racks along a rowin a datacenter 100. In at least one embodiment, plumbing of a secondarycooling loop 108, including coolant manifolds 118, 116, and 114 may beimproved by at least one embodiment herein. In at least one embodiment,a chiller 120 may be provided in a primary cooling loop withindatacenter 102 to support cooling before a cooling tower. In at leastone embodiment, additional cooling loops that may exist in a primarycontrol loop and that provide cooling external to a rack and external toa secondary cooling loop, may be taken together with a primary coolingloop and is distinct from a secondary cooling loop, for this disclosure.

In at least one embodiment, in operation, heat generated within servertrays of provided racks 110 may be transferred to a coolant exiting oneor more racks 110 via flexible tubing of a row manifold 114 of a secondcooling loop 108. In at least one embodiment, second coolant (in asecondary cooling loop 108) from a CDU 112, for cooling provided racks110, moves towards one or more racks 110 via provided tubing. In atleast one embodiment, second coolant from a CDU 112 passes from on oneside of a room manifold having tubing 118, to one side of a rack 110 viaa row manifold 116, and through one side of a server tray via differenttubing 114. In at least one embodiment, spent or returned second coolant(or exiting second coolant carrying heat from computing components)exits out of another side of a server tray (such as enter left side of arack and exits right side of a rack for a server tray after loopingthrough a server tray or through components on a server tray). In atleast one embodiment, spent second coolant that exits a server tray or arack 110 comes out of different side (such as exiting side) of tubing114 and moves to a parallel, but also exiting side of a row manifold116. In at least one embodiment, from a row manifold 116, spent secondcoolant moves in a parallel portion of a room manifold 118 and is goingin an opposite direction than incoming second coolant (which may also berenewed second coolant), and towards a CDU 112.

In at least one embodiment, spent second coolant exchanges its heat witha primary coolant in a primary cooling loop 106 via a CDU 112. In atleast one embodiment, spent second coolant may be renewed (such asrelatively cooled when compared to a temperature at a spent secondcoolant stage) and ready to be cycled back to through a second coolingloop 108 to one or more computing components. In at least oneembodiment, various flow and temperature control features in a CDU 112enable control of heat exchanged from spent second coolant or flow ofsecond coolant in and out of a CDU 112. In at least one embodiment, aCDU 112 may be also able to control a flow of primary coolant in primarycooling loop 106.

In at least one embodiment, exemplary server-level features 130 can beutilized as illustrated in FIG. 1B, which is associated with a coolingsystem subject to improvements described herein. In at least oneembodiment, server-level features 130 as illustrated in FIG. 1B can beassociated with a cold plate that is in turn associated with anintegrated server flow-through fixture or manifold with a state sensor.In at least one embodiment, server-level features 130 include a servertray or box 132. In at least one embodiment, a server tray or box 132includes a server manifold 134 to be intermediately coupled betweenprovided cold plates 140A-D of a server tray or box 132 and rackmanifolds of a rack hosting a server tray or box 132. In at least oneembodiment, a server tray or box 132 includes one or more cold plates140A-C associated with one or more computing or datacenter components ordevices 180A-C. In at least one embodiment, one or more cold plates140A-C may be dual-cooling-enabled cold plates having a first distinctpath 164 capable of cooling using a first coolant and second a seconddistinct path 170 capable of cooling using a second coolant concurrentlywith a first coolant or at separate times. In at least one embodiment,such first distinct path 164 and second distinct path 170 are fins ortubes.

In at least one embodiment, at least one heat sink 140D includes finsand is exposed to an environment of a server tray or box 132 so thatcold air from a cold aisle 122 can be used as cooling media through suchfins to cool a heat sink 140D before such cold air exits to a hot aisle124. In at least one embodiment, an associated computing device 180Dbenefits from cooling provided by such heat sink 140D. In at least oneembodiment, therefore, cooling media may be air or single-phase fluid,with such single-phase fluid being a coolant that is to flow through anintegrated server flow-through fixture or manifold having a statesensor.

In at least one embodiment, one or more server-level cooling loops 144A,B may be provided between a server manifold 134 and one or more coldplates 140A-C for single or dual-cooling-enabled cold plates. In atleast one embodiment, each server-level cooling loop 144A; B includes aninlet line 142A and an outlet line 142B. In at least one embodiment,when there are series configured cold plates 140A, B, an intermediateline 146 may be provided. In at least one embodiment, however, for anintegrated server flow-through fixture or manifold with a state sensor,distinct fluid paths, via provided lines 176A, may be establishedbetween channels (illustrated as broken lines) within a dual purposemanifold 134 adapted to pass a first coolant through first providedlines 136A, B and a second coolant through second provided lines 138A, Bassociated with such provided channels. In at least one embodiment,there may be separate server cooling manifolds for each type of coolantused.

In at least one embodiment, one or more cold plates 140A-C may be onlysingle-coolant-enabled cold plates or only dual-coolant-enabled coldplates. In at least one embodiment, one or more cold plates 140A-C, whenadapted for dual purpose, may support distinct ports and channels for afirst secondary coolant of a secondary cooling loop and for a secondsecondary coolant (or local coolant) circulated from a local coolantsource. In at least one embodiment, a first secondary coolant forcooling may be provided to a server manifold 134 via provided inlet andoutlets 136A, 136B. In at least one embodiment, a second secondarycoolant may be provided to a server manifold 134 via provided inlet andoutlets 138A, 138B. In at least one embodiment, all such manifolds,lines, or loops may be terminated using flow controllers havingmechanical coupling and electrical coupling features. In at least oneembodiment, electrical coupling features enable at least one processorto control aspects of a flow controller for a cold plate that isassociated with an integrated server flow-through fixture or manifoldwith a state sensor.

In at least one embodiment, a server tray 132 is an immersive-cooledserver tray that may be flooded by fluid. In at least one embodiment, afluid for an immersive-cooled server tray may be a dielectric engineeredfluid capable of being used in an immersive-cooled server. In at leastone embodiment, a secondary coolant or local coolant may be used to coolengineered fluid. In at least one embodiment, a local coolant may beused to cool engineered fluid when a primary cooling loop associatedwith a secondary cooling loop circulating a secondary coolant has failedor is failing. In at least one embodiment, at least one cold platetherefore has ports for a secondary cooling loop and for a local coolantcooling loop from a local coolant source that is part of a systemadapted for an integrated server flow-through fixture or manifold with astate sensor. In at least one embodiment, such a cold plate can supporta local coolant that may be activated in an event of a failure in aprimary cooling loop.

In at least one embodiment, at least one dual-cooling cold plate 140B;150 may be configured to work alongside regular cold plates 140A, C. Inat least one embodiment, a three-dimensional (3D) blow-up illustration(cold plate 150) provides internal detail of at least some features thatmay be included in a dual-cooling cold plate or a regular cold plate. Inat least one embodiment, a tear-through of a cold plate 150 illustratesmicrochannels 170 and a distinct section for tubes 164 functioning asheat dissipation features, as illustrated in FIGS. 1A, B. In at leastone embodiment, a distinct second section may be provided side-by-sideand having heat dissipation features in at least a part of such a coldplate. In at least one embodiment, a local coolant-enabled cold platemay have only tubes 164 and no microchannels 170 therein.

In at least one embodiment, a dual-cooling cold plate 150 has distinctpaths 164, 170 for secondary coolant of a secondary cooling loop, forlocal coolant of a local cooling loop, and for local coolant from alocal coolant source. In at least one embodiment, in a use case of animmersive-cooled server, fluid that may be a dielectric engineered fluidmay be adapted for both, a cold plate application and animmersive-cooled server tray application. In at least one embodiment,some microchannels 170 are paths provided by fins or other such aspectsthat raise internally and perpendicularly to a base of a cold platesection, and that have gaps therebetween for coolant or fluid flow. Inat least one embodiment, some microchannels 170 are fluid pathways in adifferent cold plate section of a cold plate 150.

In at least one embodiment, reference to a cold plate, along with itsdual-cooling features, may imply a reference to a cold plate that cansupport at least two types of cooling loops, unless otherwise stated. Inat least one embodiment, both types of colds plates receive at leastlocal coolant for cooling, but one type can support both, a secondarycooling loop or a local cooling loop and local coolant from a localcoolant source. In at least one embodiment, a standard coolant, such asfacility water may be used in a secondary cooling loop.

In at least one embodiment, a fluid or local coolant may only supportcold plate usage and may not be available for immersive cooling. In atleast one embodiment, each type of cold plate receives local coolantthat may be associated with different secondary or local coolant fromrespective local cooling loops or other cooling loops interfacing with aprimary cooling loop. In at least one embodiment, in situations wheredifferent fluids (such as secondary coolants and local coolants) areused in a datacenter cooling system, then a secondary or local coolingloop may be suited for a dual-cooling cold plate, along with localcoolant. In at least one embodiment, secondary or local coolant may besupported by an integrated server flow-through fixture or manifold witha state sensor, so that different channels may be used for each of alocal coolant and for different secondary coolants.

In at least one embodiment, a dual-cooling cold plate 150 is adapted toreceive two types of fluids (such as a secondary coolant and a localcoolant) and to keep two types of fluids distinct from each other viatheir distinct ports 152, 172; 168, 162 and their distinct paths 164,170, such as by distinct sections separated by gaskets and plates (suchas in a gasket type cold plate). In at least one embodiment, fluid lines156, 158, 166, 174 are associated with such ports 152, 162, 168, 172,via respective flow controllers. In at least one embodiment, eachdistinct path is a cooling or flow path. In at least one embodiment,fluid (such as a local coolant or a secondary coolant) from a localcoolant source and a secondary coolant may be provided simultaneously toaddress additional cooling requirements. In at least one embodiment,distinct ports and paths may support different sources that may beprovided to address a higher cooling requirement from an associatedcomputing device.

In at least one embodiment, a dual-cooling cold plate 150 includes ports152, 262 to receive a local coolant into a cold plate 150, to enablesuch local coolant to pass through a cold plate 150, and to enable suchlocal coolant to pass out of a cold plate 150. In at least oneembodiment, a dual-cooling cold plate 150 includes ports 168, 172 toreceive a secondary coolant into a cold plate 150, to enable suchsecondary coolant to pass through a cold plate 150, and to pass asecondary coolant out of a cold plate 150. In at least one embodiment,provided ports 152, 162 may have valve covers 154 that may bedirectional to enable flow of local coolant or secondary coolant througha cold plate 150.

In at least one embodiment, provided valve covers 154 are mechanicalfeatures of associated flow controllers that also have correspondingelectronic features (such as at least one processor to executeinstructions stored in associated memory and to control mechanicalfeatures for associated flow controllers). In at least one embodiment,sensors can be used to provide feedback to adjust inlet local coolantthrough a cold plate.

In at least one embodiment, each valve may be actuated by an electronicfeature of an associated flow controller. In at least one embodiment,electronic and mechanical features of provided flow controllers areintegrated. In at least one embodiment, electronic and mechanicalfeatures of provided flow controllers are physically distinct. In atleast one embodiment, reference to flow controllers may be to one ormore of provided electronic and mechanical features or to their unionbut is at least in reference to features enabling control of flow ofcoolant or fluid through each cold plate or an immersion-cooled servertray or box.

In at least one embodiment, electronic features of provided flowcontrollers receive control signals and assert control over mechanicalfeatures. In at least one embodiment, electronic features of providedflow controllers may be actuators or other electronic parts of othersimilar electromechanical features. In at least one embodiment, flowpumps may be used as flow controllers. In at least one embodiment,impellers, pistons, or bellows may be mechanical features, and anelectronic motor and circuitry form electronic features of provided flowcontrollers. In at least one embodiment, circuitry of provided flowcontrollers may include processors, memories, switches, sensors, andother components, altogether forming electronic features of providedflow controllers.

In at least one embodiment, provided ports 152, 162, 168, 172 ofprovided flow controllers are adapted to either allow entry or to allowegress of an immersive fluid. In at least one embodiment, flowcontrollers 148 (capable of acting as an expansion valve) may beassociated with fluid lines 176A; B (also 156, 158) that enable entryand egress of a local coolant to a cold plate 140A-C. In at least oneembodiment, other flow controllers may be similarly associated withcoolant lines 142A, 146, 142B (also 166, 174) to enable entry and egressof a secondary coolant to a cold plate 140B, D.

In at least one embodiment, a local coolant enters provided fluid lines176A, B via dedicated inlet and outlet lines 138A, B. In at least oneembodiment, a server manifold 134 is adapted with channels therein(illustrated by dotted or broken lines) to support distinct paths todistinct fluid lines 176A, B (also 156, 158) and to any remaining loops144A, B that are associated with secondary coolant inlet and outletlines 136A, B. In at least one embodiment, there may be multiplemanifolds to support integrated server flow-through fixture or manifoldwith a state sensor for a local coolant and a distinct secondarycoolant. In at least one embodiment, there may be multiple manifolds tosupport entry and egress, distinctly, for each of a local coolant and ofa secondary coolant. In at least one embodiment, a local coolant issingularly used without a secondary cooling loop.

In at least one embodiment, FIGS. 2A, 2B illustrate exemplary features200, 220 associated with an integrated server flow-through fixture ormanifold with a state sensor for a datacenter cooling system. In atleast one embodiment, such a state sensor to determine a state of aflow-through fixture or manifold does so by determining if coolant isflowing there through, by determining a flow rate or volume of such acoolant, by determining a pH of such a coolant, or by determining otherphysical or chemical characteristics of such a coolant. In at least oneembodiment, a datacenter cooling system, therefore, includes a servertray or box 202C having a surface 204 with one or more flow-throughfixtures 206 extending on both sides of a surface 204. In at least oneembodiment, multiple flow-through fixtures 206 may be provided so thatentry of coolant occurs through one of such flow-through fixtures 206and egress of coolant occurs through a different one of suchflow-through fixtures 206.

In at least one embodiment, each flow-through fixture or manifold 206includes an inward coupling 216A, an outward coupling 216B, a flowcontroller 224A, and a state sensor 222. In at least one embodiment,each flow-through fixture or manifold 206 may include a further flowcontroller and a further state sensor. In at least one embodiment, astate sensor 222 can monitor a flow-through fixture or manifold 206. Inat least one embodiment, such monitoring may be to a state of aflow-through fixture or manifold 206.

In at least one embodiment, one or more of a first flow controller or asecond flow controller can change a flow of a coolant through aflow-through fixture or manifold 206. In at least one embodiment, suchone or more of a first flow controller or a second flow controller canalso selectively trap a portion of a coolant within a flow-throughfixture or manifold 206. In at least one embodiment, this allowsdecoupling of an inward coupling 216A or an outward coupling 216Bwithout a leak from a further flow controller 218; 236.

In at least one embodiment, an inward coupling 216A or an outwardcoupling 216B includes push-coupling or threaded-coupling features toenable an external flow controller 218; 236 to fluidly communicate withone or more of a first flow controller or a second flow controller. Inat least one embodiment a state sensor 222 may be adapted to monitor astate of a flow rate, a flow volume, or a chemistry of a coolant that isto pass through a flow-through fixture 206.

In at least one embodiment, multiple flow controllers are providedwithin a flow-through fixture or manifold 206 or a further flowcontroller is provided to support a single flow controller 224 of aflow-through fixture or manifold 206. In at least one embodiment, suchone flow controller 224 may close within a flow-through fixture ormanifold 206 to retain at least a portion of coolant within aflow-through fixture or manifold 206 and along a flow path provided viaillustrated lines 210A-E of a server tray or box 202.

In at least one embodiment, two flow controllers 224 within a sameflow-through fixture or manifold 206 may be adapted to closeconcurrently. In at least one embodiment, two flow controllers 224between two different flow controllers of two different flow-throughfixtures 206 may be adapted to close concurrently. In at least oneembodiment, this is to selectively trap a portion of a coolant withinone or more flow-through fixtures or manifolds 206 and within at leastone of such one or more flow-through fixtures or manifolds 206. In atleast one embodiment, such a selective trap is to occur at least ondisconnection of a server tray or box 202. In at least one embodiment,this prevents leaks when removing a server tray or box from an externalcoupling, prevents leaks when removing a cold plate 212A; 212B; 212C;212D from a server tray or box 202, and prevents leaks when removing oneor more server cooling manifolds 208A, 208B from a server tray or box202.

In at least one embodiment, flow-through fixtures or manifolds 206 maybe integrated with server cooling manifolds 208A, B. In at least oneembodiment, a benefit of keeping such flow-through fixtures or manifoldsdifferent from a server cooling manifold 208A, B is to enablereplacement of parts and manifolds that would otherwise requirereplacement of a server tray or box if an issue is to be determined witha flow controller or sensor of such flow-through fixtures or manifolds.

In at least one embodiment, coolant enters a server tray or box 202 viaa first flow-through fixture or manifold 206 that may be coupled, at itsoutward coupling 216B, to a rack-side flow controller 236A of a rackcooling inlet manifold 234A. In at least one embodiment, coolant flowsthrough one or more flow controllers 224. In at least one embodiment,FIG. 2B illustrates an inward coupling 216A with a first flow controller224 and an outward coupling 216B with a second flow controller 224. Inat least one embodiment, one flow controller may be used for controllinga change in a state for a flow-through fixture or manifold 206 and asecond flow controller may be used for a selective trap for at least aportion of a coolant within a flow-through fixture or manifold 206.

In at least one embodiment, as illustrated, valves covers 226 that areactuated to different openness or closeness within a flow-throughfixture or manifold 206 enable a change in a state (such as a flow rateand a flow volume) of a coolant there through. In at least oneembodiment, impeller pumps 228 that are controlled at differentrevolutions per minute (rpm) may be used to change a state of a coolantthere through. In at least one embodiment, valve covers 226 may be usedfor a selective trap for at least a portion of a coolant within aflow-through fixture or manifold 206. In at least one embodiment, animpeller pump 228 may be enabled to do this, but may require anassociated valve cover in addition to an impeller. In at least oneembodiment, a flow-through fixture or manifold 206 may have acombination of a valve cover and an impeller flow controllerrepresenting two different flow controllers or a single flow controllerdepending on a configuration to perform different actions (such aschanging flow rate and providing a selective trap) or to achieve asingle action (such as changing flow rate or providing a selectivetrap).

In at least one embodiment, a surface 204 having such a flow-throughfixture or manifold 206 is a rear surface of a server tray or box 202.In at least one embodiment, this is to enable push installation of aserver tray or box 202 into a rack. In at least one embodiment, suchpush installation is to engage at least an outward coupling 216B of aflow-through fixture or manifold 206 with an external coupling for acoolant to flow from a rack cooling inlet manifold 234A to at least onecold plate 212A-D of a server tray or box 202. In at least oneembodiment, one or more flow controllers 224 are concurrently triggeredto open or allow flow of a coolant upon such a push-installationperformed.

In at least one embodiment, coolant flows through a flow-through fixtureor manifold 206, a further flow controller 218, an inlet coolant tube210A, and a server cooling manifold 208A that may be an inlet servercooling manifold. In at least one embodiment, such a server coolingmanifold 208A may be used so that multiple server-level cooling loopsmay be established without further flow-through fixtures for eachserver-level cooling loop. In at least one embodiment, at least twodistinct server-level cooling loops are illustrated in FIG. 2A. In atleast one embodiment, coolant enters a first cold plate 212A, from aserver cooling manifold 208A via a cold pate coolant tube 210B, to coolan associated computing device 214. In at least one embodiment, heat isremoved from a such an associated computing device 214 by transfer to acoolant.

In at least one embodiment, if serial cold plates are used in aserver-level cooling loop, then an intermediate coolant tube 210Cenables flow of coolant from a first cold plate 212A to a second coldplate 212B that is associated with a different computing device 214. Inat least one embodiment, an outlet coolant tube 210D enables passescoolant back to a server cooling manifold 208B that may be an outletserver cooling manifold. In at least one embodiment, however, a singlecooling manifold having channels for inlet and for outlet may be usedwith one or more flow-through fixtures 206. In at least one embodiment,each such coolant tube or line may be associated with a flow controllerso that leaks are prevented upon disconnection of any such coolant tubeor line.

In at least one embodiment, coolant then flows out from a server coolingmanifold 208B through another flow-through fixture or manifold 206 andto a rack outlet cooling manifold 234B that is associated with aflow-through fixture or manifold 206 at an outlet side via its own flowcontrollers 236B. In at least one embodiment, one or more state sensors222 may be provided in each flow-through fixture or manifold 206. In atleast one embodiment, such state sensors 222 may be coupled to aprocessor that is external to such a flow-through fixture or manifold206. In at least one embodiment, multiple state sensors 222 communicateto an external processor that may be a part of a BMS or a buildingmanagement system. In at least one embodiment, a control unit (such as alast server tray or box 308 of a rack 302 in FIG. 3 ) may be provided asa server tray or box form-factor within a rack to control all flowcontrollers within a rack.

In at least one embodiment, a processor may be adapted to receive inputfrom a state sensor 222. In at least one embodiment, such input orsensor input may be about a state of a flow-through fixture or manifold206. In at least one embodiment, a state may be in reference to a flowrate, a flow volume, or a chemistry of a coolant to flow through aflow-through fixture or manifold 206. In at least one embodiment, anabsence of a flow rate, a flow volume, or a chemistry may be also astate of a flow-through fixture or manifold 206 that is sensed by astate sensor and provided to a processor. In at least one embodiment,based at least in part on such an input, a processor to cause a changefor a flow-through fixture or manifold 206, by an action on a flowcontroller 224. In at least one embodiment, an action may be an outputfrom a processor to a flow controller 224 to trigger a pump or to open avalve cover from a seal portion 232 of a flow-through fixture ormanifold 206. In at least one embodiment, multiple state sensors 222when used with a single flow-through fixture or manifold 206 may provideinput that is used by a processor as a relative input to sense a changein flow rate instantaneously without a need to determine this fromdifferent times of a reported flow rate of a single state sensor 222.

In at least one embodiment, a processor may include one or more neuralnetworks that may be adapted to receive input from a state sensor 222 ofa flow-through fixture or manifold 206. In at least one embodiment, suchone or more neural networks can infer a state of a flow-through fixtureor manifold 206 based in part on prior inputs and prior states of aflow-through fixture or manifold 206. In at least one embodiment, astate sensor 222 may be a self-calibrating sensor. In at least oneembodiment, a self-calibrating sensor can function as a state sensorbecause it includes memory having state configurations that can beloaded into a microprocessor of a state sensor 222 to change a digitalrange of a state sensor.

In at least one embodiment, such state configurations may be associatedwith different types of coolants having different ranges of measures,such as different preferred flow rates or flow volumes associated withdifferent temperatures of heat to be addressed as cooling requirementsassociated with a computing device. In at least one embodiment, suchdifferent ranges of measures may be to different ranges of pH that acoolant can operate within without being considered to degrade. In atleast one embodiment, a self-calibrating sensor 222 can provide senorinputs to at least one processor based in part on one of such stateconfigurations being defaulted from a memory to a microprocessor of astate sensor 222. In at least one embodiment, such state configurationsmay change a type that is associate with a coolant, such as PG-25®,deionized water, and HC-30®.

In at least one embodiment, a processor may include one or more circuitsand may be associated with a server tray or box 202. In at least oneembodiment, such a server tray or box 202 includes a surface 204 havinga flow-through fixture or manifold 206 extending on both sides of asurface 204. In at least one embodiment, a flow-through fixture ormanifold 206 includes an inward coupling 216A, an outward coupling 216B,a flow controller 224, and a state sensor 222. In at least oneembodiment, a processor can receive sensor inputs from a state sensor222. In at least one embodiment, a state sensor 222 may be adapted tomonitor a flow-through fixture or manifold 206. In at least oneembodiment, one or more circuits can provide signals to a flowcontroller 224 in response to such sensor inputs to cause a flowcontroller 224 to change a flow of a coolant through a flow-throughfixture or manifold 206 and to selectively trap a portion of a coolantwithin a flow-through fixture or manifold 206. In at least oneembodiment, such a portion is within a flow-through fixture or manifold206 and within a coolant tube or a server cooling manifold.

In at least one embodiment, an output of one or more of such circuitsmay be coupled to one or more of a first flow controller or a secondflow controller. In at least one embodiment, then, an output can providea first signal to one or more of a first flow controller or a secondflow controller to cause a change in a flow of a coolant through aflow-through fixture or manifold 206. In at least one embodiment, suchan output can provide a second signal to both, a first flow controllerand a second flow controller to support a selectively trap of a portionof coolant within a flow-through fixture or manifold 206.

In at least one embodiment, a processor includes an input that isadapted to receive sensor inputs from a state sensor about a state of aflow-through fixture or manifold 206. In at least one embodiment, aprocessor can cause a change for a flow-through fixture or manifold 206by an action of a first flow controller or a second flow controller. Inat least one embodiment, in each of such configurations for at least oneflow-through fixture or manifold 206 having at least one flow controller224, a second flow-through fixture or manifold 206 may be fullycontrolled by an action provided for one flow-through fixture ormanifold 206. In at least one embodiment, this is so that input forchanges may be sent to one flow controller, but are enforced at bothflow controllers or is such that change in one flow controller causes aproportional change in a second flow controller, for instance, usingpressure sensitive valve covers to also close or adjust a second flowcontroller proportional to a change enforced by a first flow controller.

In at least one embodiment, a processor can include one or more neuralnetworks that may be adapted to receive sensor inputs from a statesensor of a flow-through fixture or manifold 206. In at least oneembodiment, such one or more neural networks can infer a state of aflow-through fixture or manifold 206 based in part on prior sensorinputs and prior states of a flow-through fixture or manifold 206. In atleast one embodiment, prior sensor inputs and prior states may beprovided to one or more neural networks to determine at least arelationship that may be defined by a function that has its errorminimized. In at least one embodiment, one or more neural networks, oncetrained, will be able to infer a state of a flow-through fixture ormanifold 206 with a sensor input received in a processor processedthrough such a function.

In at least one embodiment, each of at least one processor describedthroughout FIGS. 2A-4 has inference and/or training logic 615 (as inFIG. 6A) that may include, without limitation, code and/or data storage601 to store forward and/or output weight and/or input/output data,and/or other parameters to configure neurons or layers of a neuralnetwork trained and/or used for inferencing in aspects of one or moreembodiments. In at least one embodiment, training logic 615 may include,or be coupled to code and/or data storage 601 to store graph code orother software to control timing and/or order, in which weight and/orother parameter information may be to be loaded to configure, logic,including integer and/or floating point units (collectively, arithmeticlogic units (ALUs)). In at least one embodiment, code, such as graphcode, loads weight or other parameter information into processor ALUsbased on an architecture of a neural network to which such codecorresponds. In at least one embodiment, code and/or data storage 601stores weight parameters and/or input/output data of each layer of aneural network trained or used in conjunction with one or moreembodiments during forward propagation of input/output data and/orweight parameters during training and/or inferencing using aspects ofone or more embodiments. In at least one embodiment, any portion of codeand/or data storage 601 may be included with other on-chip or off-chipdata storage, including a processor's L1, L2, or L3 cache or systemmemory.

In at least one embodiment, FIG. 3 illustrates rack-level features 300associated with an integrated server flow-through fixture or manifoldwith a state sensor for a datacenter cooling system. In at least oneembodiment, such rack-level features 300 include one or more racks 302in one or more rows. In at least one embodiment, each row may beassociated with its own cooling manifold 350 that is associated with asecondary coolant for dual purpose cold plates, although only asecondary coolant-based cooling or only a local coolant-based coolingmay be enabled for one or all of such racks 302 in FIG. 3 usingdedicated manifolds 346, 348. In at least one embodiment, some servertrays or boxes 344 may be associated with secondary coolant-basedcooling, while other server tray or boxes 338, 340 may be associatedwith a local coolant-based cooling. In at least one embodiment, in eachsuch cases, server trays or boxes 308 having an integrated serverflow-through fixture or manifold with a state sensor may be used. In atleast one embodiment, this enables plug-and-play use of server trays andboxes with minimal losses during replacement, decommissioning, orinstallation of server trays or boxes.

In at least one embodiment, flow paths may be enabled to a dual-purposecold plate 326, through one or more rack cooling manifolds 314A, 314B or346, 348 that is within a rack 302. In at least one embodiment, asingular rack cooling manifold may support entry and egress of asecondary coolant and a separate rack cooling manifold may support entryand egress of a local coolant. In at least one embodiment, however,separate rack cooling manifolds 314A, 314B may be used for each of entryand of exit of each of such secondary coolant and local coolantdepending on if both are used or if each is used independently.

In at least one embodiment, one or more flow controllers may beassociated with a rack cooling manifold to enable association with acorresponding an integrated server flow-through fixture or manifold of aserver tray or box, which allows flow of a secondary or local coolant toa cold plate within such server tray or box. In at least one embodiment,one or more flow controllers may be associated with a rack coolingmanifold 314A, B to enable association with a corresponding server-sideintegrated server flow-through fixture or manifold of a server tray orbox, which allows flow of a secondary coolant to a cold plate withinsuch server tray or box. In at least one embodiment, only one or more ofsuch groups of one or more flow controllers are provided depending onwhether secondary coolant, local coolant, or a combination is providedfor each of such provided racks 302.

In at least one embodiment, such a dual-purpose cold plate 326 isassociated with a computing device 324 that may have a coolingrequirement may be addressed by a secondary coolant, a local coolant, ora combination of coolants. In at least one embodiment, such a flow pathallows secondary or local coolant from a row cooling manifold 350 toenter into and exit from one or more rack cooling manifolds 314A, B. Inat least one embodiment, secondary or local coolant may flow 360 betweena row cooling manifold 350 and a CDU. In at least one embodiment, suchcoolant flows through a row cooling manifold 350, through an inlet 310Aof a rack 302, through a flow controller 310C adapted to switch betweenat least two coolant paths (or a coolant path and a local coolant path),through an inlet 310, and into a rack cooling manifold 314A. In at leastone embodiment, such secondary or local coolant enters a cold plate 326and addresses one cooling requirement associated with a cold plate 326and/or its associated computing device 324. In at least one embodiment,a separate flow controller than an illustrated flow controller 310C maybe used for local coolant.

In at least one embodiment, secondary or local coolant flows through afurther inlet 316 of a server tray or box 308, to a cold plate 326 of anassociated computing device 324, out of an outlet 318 of a server trayor box 308, through a rack cooling manifold 314B, into a further outlet312, through another flow controller 312C, and out of an outlet line312A to a row cooling manifold 350 that may be a same or a different rowcooling manifold than an inlet side row cooling manifold. Further, a rowcooling manifold 350 or a rack cooling manifold 314A; B may havedifferent channels therein to support inlet and outlet flows.

In at least one embodiment, for a dual cooling cold plate or a singlecoolant cold plate, a local coolant may be caused to occur via differentflow paths, such as an inlet or inlet lines from a distinct inletmanifold 346 provided at a top of a rack 302, through a channel of arack cooling manifold 314A or a dedicated local coolant manifold 346,through direct lines 320, 354, 322 to a cold plate 326, and out ofoutlet lines of a further distinct manifold 348 at a top of a rack 302.

In at least one embodiment, a rack 302 can therefore include distinctlocal coolant flow paths than secondary coolant flow paths. In at leastone embodiment, such direct lines may be available within each of aserver trays or boxes 308 of a rack 302 and may also be available withinan immersive server 352 of a rack 302. In at least one embodiment, suchlocal coolant enters a cold plate 326 and addresses a second coolingrequirement that may be associated with a cold plate 326 and/or itsassociated computing device 324. In at least one embodiment, a coldplate 326 is either a coolant cold plate, a local coolant cold plate, ora dual cooling cold plate supporting secondary coolant and localcoolant.

In at least one embodiment, datacenter-level features 400 as illustratedin FIG. 4 can be associated with a cold plate that is further associatedwith an integrated server flow-through fixture or manifold with a statesensor in a datacenter cooling system. In at least one embodiment,datacenter-level features 400, within a datacenter 402, may includeracks 404 for hosting one or more server trays or boxes; and one or moreaspects 424A, 424B, 430, 436 (such as a local coolant distribution unit(LCDU) 424B and a local coolant cooling unit 424A, and dedicatedmanifolds 430, 436) for an integrated server flow-through fixture ormanifold with a state sensor.

In at least one embodiment, a local coolant manifolds 430, 436 arecoupled to an LCDU 424B to enable local coolant to be provided, vialines 428, 426, 434, to multiple racks 404. In at least one embodiment,an LCDU 424B is able to distribute local coolant to multiple manifoldsusing internal flow controllers and sensors to control flow, but is alsocapable of controlled heat exchange with another media, such as anotherlocal coolant, a fan, or a primary coolant. In at least one embodiment,at least such secondary and local coolant cooling may be operateddistinct from a secondary cooling loop 412 and a primary cooling loop422, such as by using a local coolant cooling unit 424A, if anotherlocal coolant is used to cool a local coolant for a cold plate without aCDU 406, a chilling tower 408, and a primary cooling loop 422. In atleast one embodiment, one or more secondary cooling row manifolds 410may be provided for distributing secondary coolant from a CDU 406.

In at least one embodiment, for coolant-based cooling, one or moreprimary cooling row manifolds (such as piping or lines making up part ofa primary cooling loop 422) may be provided for distributing primarycoolant to a CDU 406 and to an LCDU cooling unit 424A from a chillingfacility 408. In at least one embodiment, various flow controllers 412A,B (also in other Figures herein), and inlet and outlet lines 412, 414,416, 418, 420 are provided or coolant distribution. In at least oneembodiment, flow controllers 412A, B and such inlet and outlet lines412, 414, 416, 418 are supported by distinct flow controllers thatenable different flow paths, such as a coolant flow path 436 forsecondary coolant, which is distinct from a local coolant flow path 426,428, 434.

In at least one embodiment, at least one processor may be providedwithin a control system or unit. In at least one embodiment, such acontrol system or unit may be a form-factor of multiple server units orboxes. In at least one embodiment, this allows for at least one rack tobe self-sufficient towards any cooling requirements to be addressedusing at least local coolant. In at least one embodiment, such at leastone processor may be part of a building management system (BMS). In atleast one embodiment, such at least one processor may be associated withmultiple flow controllers to enable different flow paths discussedthroughout herein. In at least one embodiment, at least one processorcan determine a cooling requirement associated with at least onecomputing device. In at least one embodiment, at least one processor canperform enabling of requisite flow paths and disabling of other flowpaths to address such cooling requirements from single-phase or localcoolant cooling.

In at least one embodiment, an inference and/or training logic 615 of atleast one processor may be part of a building management system (BMS)for an integrated server flow-through fixture or manifold with a statesensor of local coolant for a datacenter cooling system. In at least oneembodiment, a determination to engage a certain feature of an integratedserver flow-through fixture or manifold with a state sensor and a flowcontroller therein may be provided to one or more neural networks of aninference and/or training logic 615 to cause one or more neural networksto infer which feature and which flow controllers to gracefully engageor disengage.

FIG. 5 illustrates a method 500 associated with a datacenter coolingsystem of FIGS. 2A-4 , according to at least one embodiment. In at leastone embodiment, a method 500 herein includes a step for providing (502)a server tray or box having a surface with a flow-through fixture ormanifold extending on both sides of such a surface. In at least oneembodiment, a method 500 herein further includes enabling (504) aninward coupling, an outward coupling, a flow controller, and a statesensor for a flow-through fixture. In at least one embodiment, thisenabling (504) feature may be a manufacture feature performed duringmanufacturing or may be an installation, decommissioning, or replacementfeature performed during installation, decommissioning, or replacementof a server tray or box. In at least one embodiment, exposing an inwardcoupling, an outward coupling, a flow controller, and a state sensor forengagement or disengagement during installation, decommissioning, orreplacement may be considered an enabling (504) feature of a method 500herein.

In at least one embodiment, monitoring (506), using a state sensor, fora state of a flow-through fixture or manifold may be provided in such amethod 500. In at least one embodiment, verification (508) may beperformed to determine that such a change in a state of a flow-throughfixture or manifold has occurred. In at least one embodiment, this maybe a determination at manufacture, installation, or installation time.

In at least one embodiment, verification may be confirmed by an act ofcomparing a received input with a threshold or by a neural network orother automated feature that makes such a verification or comparisonoccur. In at least one embodiment, a step 506 may be repeated till achange has been verified. In at least one embodiment, a method 500herein includes enabling (510) a flow controller of a flow-throughfixture or manifold to change a flow of a coolant through a flow-throughfixture or manifold and to selectively trap a portion of a coolantwithin a flow-through fixture.

In at least one embodiment, a method (500) herein includes a step or asub-step for enabling, using an inward coupling or an outward couplingthat include push-coupling or threaded-coupling features, an externalflow controller to fluidly communicate with a flow controller of aflow-through fixture. In at least one embodiment, a method (500) hereinincludes a step or a sub-step for monitoring, using a state sensor, astate of a flow rate, a flow volume, or a chemistry of a coolantassociated with a flow-through fixture or manifold as part of amonitoring (506) step in a method 500 herein.

In at least one embodiment, a method (500) herein includes a step or asub-step for closing, concurrently, a flow controller of a flow-throughfixture or manifold and a further flow controller to selectively trap aportion of a coolant within a flow-through fixture, at least ondisconnection of a server tray or box. In at least one embodiment, amethod (500) herein includes a step or a sub-step for locating a surfacehaving a flow-through fixture or manifold on a rear of a server tray orbox to enable push installation of a server tray or box into a rack. Inat least one embodiment, a push installation can engage at least anoutward coupling of a flow-through fixture or manifold with an externalcoupling for a coolant to flow from a rack cooling manifold to at leastone cold plate of a server tray or box.

In at least one embodiment, a method (500) herein includes a step or asub-step for receiving input at a processor from a state sensor. In atleast one embodiment, an input may be associated with a state of aflow-through fixture. In at least one embodiment, a method (500) hereinincludes causing, by an action of a processor on a flow controller, achange of a flow of a coolant and a selective trap of a portion of acoolant. In at least one embodiment, a method (500) herein includesusing one or more neural networks to receive input from a state sensorof a flow-through fixture. In at least one embodiment, a method (500)herein includes inferring by one or more neural networks a state of aflow-through fixture or manifold based in part on prior inputs and priorstates of a flow-through fixture.

Inference and Training Logic

FIG. 6A illustrates inference and/or training logic 615 used to performinferencing and/or training operations associated with one or moreembodiments. Details regarding inference and/or training logic 615 areprovided below in conjunction with FIGS. 6A and/or 6B.

In at least one embodiment, inference and/or training logic 615 mayinclude, without limitation, code and/or data storage 601 to storeforward and/or output weight and/or input/output data, and/or otherparameters to configure neurons or layers of a neural network trainedand/or used for inferencing in aspects of one or more embodiments. In atleast one embodiment, training logic 615 may include, or be coupled tocode and/or data storage 601 to store graph code or other software tocontrol timing and/or order, in which weight and/or other parameterinformation is to be loaded to configure, logic, including integerand/or floating point units (collectively, arithmetic logic units(ALUs)). In at least one embodiment, code, such as graph code, loadsweight or other parameter information into processor ALUs based on anarchitecture of a neural network to which such code corresponds. In atleast one embodiment, code and/or data storage 601 stores weightparameters and/or input/output data of each layer of a neural networktrained or used in conjunction with one or more embodiments duringforward propagation of input/output data and/or weight parameters duringtraining and/or inferencing using aspects of one or more embodiments. Inat least one embodiment, any portion of code and/or data storage 601 maybe included with other on-chip or off-chip data storage, including aprocessor's L1, L2, or L3 cache or system memory.

In at least one embodiment, any portion of code and/or data storage 601may be internal or external to one or more processors or other hardwarelogic devices or circuits. In at least one embodiment, code and/or codeand/or data storage 601 may be cache memory, dynamic randomlyaddressable memory (“DRAM”), static randomly addressable memory(“SRAM”), non-volatile memory (e.g., flash memory), or other storage. Inat least one embodiment, a choice of whether code and/or code and/ordata storage 601 is internal or external to a processor, for example, orcomprising DRAM, SRAM, flash or some other storage type may depend onavailable storage on-chip versus off-chip, latency requirements oftraining and/or inferencing functions being performed, batch size ofdata used in inferencing and/or training of a neural network, or somecombination of these factors.

In at least one embodiment, inference and/or training logic 615 mayinclude, without limitation, a code and/or data storage 605 to storebackward and/or output weight and/or input/output data corresponding toneurons or layers of a neural network trained and/or used forinferencing in aspects of one or more embodiments. In at least oneembodiment, code and/or data storage 605 stores weight parameters and/orinput/output data of each layer of a neural network trained or used inconjunction with one or more embodiments during backward propagation ofinput/output data and/or weight parameters during training and/orinferencing using aspects of one or more embodiments. In at least oneembodiment, training logic 615 may include, or be coupled to code and/ordata storage 605 to store graph code or other software to control timingand/or order, in which weight and/or other parameter information is tobe loaded to configure, logic, including integer and/or floating pointunits (collectively, arithmetic logic units (ALUs)).

In at least one embodiment, code, such as graph code, causes a loadingof weight or other parameter information into processor ALUs based on anarchitecture of a neural network to which such code corresponds. In atleast one embodiment, any portion of code and/or data storage 605 may beincluded with other on-chip or off-chip data storage, including aprocessor's L1, L2, or L3 cache or system memory. In at least oneembodiment, any portion of code and/or data storage 605 may be internalor external to one or more processors or other hardware logic devices orcircuits. In at least one embodiment, code and/or data storage 605 maybe cache memory, DRAM, SRAM, non-volatile memory (e.g., flash memory),or other storage. In at least one embodiment, a choice of whether codeand/or data storage 605 is internal or external to a processor, forexample, or comprising DRAM, SRAM, flash memory or some other storagetype may depend on available storage on-chip versus off-chip, latencyrequirements of training and/or inferencing functions being performed,batch size of data used in inferencing and/or training of a neuralnetwork, or some combination of these factors.

In at least one embodiment, code and/or data storage 601 and code and/ordata storage 605 may be separate storage structures. In at least oneembodiment, code and/or data storage 601 and code and/or data storage605 may be a combined storage structure. In at least one embodiment,code and/or data storage 601 and code and/or data storage 605 may bepartially combined and partially separate. In at least one embodiment,any portion of code and/or data storage 601 and code and/or data storage605 may be included with other on-chip or off-chip data storage,including a processor's L1, L2, or L3 cache or system memory.

In at least one embodiment, inference and/or training logic 615 mayinclude, without limitation, one or more arithmetic logic unit(s)(“ALU(s)”) 610, including integer and/or floating point units, toperform logical and/or mathematical operations based, at least in parton, or indicated by, training and/or inference code (e.g., graph code),a result of which may produce activations (e.g., output values fromlayers or neurons within a neural network) stored in an activationstorage 620 that are functions of input/output and/or weight parameterdata stored in code and/or data storage 601 and/or code and/or datastorage 605. In at least one embodiment, activations stored inactivation storage 620 are generated according to linear algebraic andor matrix-based mathematics performed by ALU(s) 610 in response toperforming instructions or other code, wherein weight values stored incode and/or data storage 605 and/or data storage 601 are used asoperands along with other values, such as bias values, gradientinformation, momentum values, or other parameters or hyperparameters,any or all of which may be stored in code and/or data storage 605 orcode and/or data storage 601 or another storage on or off-chip.

In at least one embodiment, ALU(s) 610 are included within one or moreprocessors or other hardware logic devices or circuits, whereas inanother embodiment, ALU(s) 610 may be external to a processor or otherhardware logic device or circuit that uses them (e.g., a co-processor).In at least one embodiment, ALUs 610 may be included within aprocessor's execution units or otherwise within a bank of ALUsaccessible by a processor's execution units either within same processoror distributed between different processors of different types (e.g.,central processing units, graphics processing units, fixed functionunits, etc.). In at least one embodiment, code and/or data storage 601,code and/or data storage 605, and activation storage 620 may share aprocessor or other hardware logic device or circuit, whereas in anotherembodiment, they may be in different processors or other hardware logicdevices or circuits, or some combination of same and differentprocessors or other hardware logic devices or circuits. In at least oneembodiment, any portion of activation storage 620 may be included withother on-chip or off-chip data storage, including a processor's L1, L2,or L3 cache or system memory. Furthermore, inferencing and/or trainingcode may be stored with other code accessible to a processor or otherhardware logic or circuit and fetched and/or processed using aprocessor's fetch, decode, scheduling, execution, retirement and/orother logical circuits.

In at least one embodiment, activation storage 620 may be cache memory,DRAM, SRAM, non-volatile memory (e.g., flash memory), or other storage.In at least one embodiment, activation storage 620 may be completely orpartially within or external to one or more processors or other logicalcircuits. In at least one embodiment, a choice of whether activationstorage 620 is internal or external to a processor, for example, orcomprising DRAM, SRAM, flash memory or some other storage type maydepend on available storage on-chip versus off-chip, latencyrequirements of training and/or inferencing functions being performed,batch size of data used in inferencing and/or training of a neuralnetwork, or some combination of these factors.

In at least one embodiment, inference and/or training logic 615illustrated in FIG. 6A may be used in conjunction with anapplication-specific integrated circuit (“ASIC”), such as a TensorFlow®Processing Unit from Google, an inference processing unit (IPU) fromGraphcore™, or a Nervana® (e.g., “Lake Crest”) processor from IntelCorp. In at least one embodiment, inference and/or training logic 615illustrated in FIG. 6A may be used in conjunction with centralprocessing unit (“CPU”) hardware, graphics processing unit (“GPU”)hardware or other hardware, such as field programmable gate arrays(“FPGAs”).

FIG. 6B illustrates inference and/or training logic 615, according to atleast one embodiment. In at least one embodiment, inference and/ortraining logic 615 may include, without limitation, hardware logic inwhich computational resources are dedicated or otherwise exclusivelyused in conjunction with weight values or other informationcorresponding to one or more layers of neurons within a neural network.In at least one embodiment, inference and/or training logic 615illustrated in FIG. 6B may be used in conjunction with anapplication-specific integrated circuit (ASIC), such as TensorFlow®Processing Unit from Google, an inference processing unit (IPU) fromGraphcore™, or a Nervana® (e.g., “Lake Crest”) processor from IntelCorp. In at least one embodiment, inference and/or training logic 615illustrated in FIG. 6B may be used in conjunction with centralprocessing unit (CPU) hardware, graphics processing unit (GPU) hardwareor other hardware, such as field programmable gate arrays (FPGAs). In atleast one embodiment, inference and/or training logic 615 includes,without limitation, code and/or data storage 601 and code and/or datastorage 605, which may be used to store code (e.g., graph code), weightvalues and/or other information, including bias values, gradientinformation, momentum values, and/or other parameter or hyperparameterinformation. In at least one embodiment illustrated in FIG. 6B, each ofcode and/or data storage 601 and code and/or data storage 605 isassociated with a dedicated computational resource, such ascomputational hardware 602 and computational hardware 606, respectively.In at least one embodiment, each of computational hardware 602 andcomputational hardware 606 comprises one or more ALUs that performmathematical functions, such as linear algebraic functions, only oninformation stored in code and/or data storage 601 and code and/or datastorage 605, respectively, result of which is stored in activationstorage 620.

In at least one embodiment, each of code and/or data storage 601 and 605and corresponding computational hardware 602 and 606, respectively,correspond to different layers of a neural network, such that resultingactivation from one storage/computational pair 601/602 of code and/ordata storage 601 and computational hardware 602 is provided as an inputto a next storage/computational pair 605/606 of code and/or data storage605 and computational hardware 606, in order to mirror a conceptualorganization of a neural network. In at least one embodiment, each ofstorage/computational pairs 601/602 and 605/606 may correspond to morethan one neural network layer. In at least one embodiment, additionalstorage/computation pairs (not shown) subsequent to or in parallel withstorage/computation pairs 601/602 and 605/606 may be included ininference and/or training logic 615.

Neural Network Training and Deployment

FIG. 7 illustrates training and deployment of a deep neural network,according to at least one embodiment. In at least one embodiment,untrained neural network 706 is trained using a training dataset 702. Inat least one embodiment, training framework 704 is a PyTorch framework,whereas in other embodiments, training framework 704 is a TensorFlow,Boost, Caffe, Microsoft Cognitive Toolkit/CNTK, MXNet, Chainer, Keras,Deeplearning4j, or other training framework. In at least one embodiment,training framework 704 trains an untrained neural network 706 andenables it to be trained using processing resources described herein togenerate a trained neural network 708. In at least one embodiment,weights may be chosen randomly or by pre-training using a deep beliefnetwork. In at least one embodiment, training may be performed in eithera supervised, partially supervised, or unsupervised manner.

In at least one embodiment, untrained neural network 706 is trainedusing supervised learning, wherein training dataset 702 includes aninput paired with a desired output for an input, or where trainingdataset 702 includes input having a known output and an output of neuralnetwork 706 is manually graded. In at least one embodiment, untrainedneural network 706 is trained in a supervised manner and processesinputs from training dataset 702 and compares resulting outputs againsta set of expected or desired outputs. In at least one embodiment, errorsare then propagated back through untrained neural network 706. In atleast one embodiment, training framework 704 adjusts weights thatcontrol untrained neural network 706. In at least one embodiment,training framework 704 includes tools to monitor how well untrainedneural network 706 is converging towards a model, such as trained neuralnetwork 708, suitable to generating correct answers, such as in result714, based on input data such as a new dataset 712. In at least oneembodiment, training framework 704 trains untrained neural network 706repeatedly while adjust weights to refine an output of untrained neuralnetwork 706 using a loss function and adjustment algorithm, such asstochastic gradient descent. In at least one embodiment, trainingframework 704 trains untrained neural network 706 until untrained neuralnetwork 706 achieves a desired accuracy. In at least one embodiment,trained neural network 708 can then be deployed to implement any numberof machine learning operations.

In at least one embodiment, untrained neural network 706 is trainedusing unsupervised learning, wherein untrained neural network 706attempts to train itself using unlabeled data. In at least oneembodiment, unsupervised learning training dataset 702 will includeinput data without any associated output data or “ground truth” data. Inat least one embodiment, untrained neural network 706 can learngroupings within training dataset 702 and can determine how individualinputs are related to untrained dataset 702. In at least one embodiment,unsupervised training can be used to generate a self-organizing map intrained neural network 708 capable of performing operations useful inreducing dimensionality of new dataset 712. In at least one embodiment,unsupervised training can also be used to perform anomaly detection,which allows identification of data points in new dataset 712 thatdeviate from normal patterns of new dataset 712.

In at least one embodiment, semi-supervised learning may be used, whichis a technique in which in training dataset 702 includes a mix oflabeled and unlabeled data. In at least one embodiment, trainingframework 704 may be used to perform incremental learning, such asthrough transferred learning techniques. In at least one embodiment,incremental learning enables trained neural network 708 to adapt to newdataset 712 without forgetting knowledge instilled within trained neuralnetwork 708 during initial training.

In at least one embodiment, training framework 704 is a frameworkprocessed in connection with a software development toolkit such as anOpenVINO (Open Visual Inference and Neural network Optimization)toolkit. In at least one embodiment, an OpenVINO toolkit is a toolkitsuch as those developed by Intel Corporation of Santa Clara, CA.

In at least one embodiment, OpenVINO is a toolkit for facilitatingdevelopment of applications, specifically neural network applications,for various tasks and operations, such as human vision emulation, speechrecognition, natural language processing, recommendation systems, and/orvariations thereof. In at least one embodiment, OpenVINO supports neuralnetworks such as convolutional neural networks (CNNs), recurrent and/orattention-based nueral networks, and/or various other neural networkmodels. In at least one embodiment, OpenVINO supports various softwarelibraries such as OpenCV, OpenCL, and/or variations thereof.

In at least one embodiment, OpenVINO supports neural network models forvarious tasks and operations, such as classification, segmentation,object detection, face recognition, speech recognition, pose estimation(e.g., humans and/or objects), monocular depth estimation, imageinpainting, style transfer, action recognition, colorization, and/orvariations thereof.

In at least one embodiment, OpenVINO comprises one or more softwaretools and/or modules for model optimization, also referred to as a modeloptimizer. In at least one embodiment, a model optimizer is a commandline tool that facilitates transitions between training and deploymentof neural network models. In at least one embodiment, a model optimizeroptimizes neural network models for execution on various devices and/orprocessing units, such as a GPU, CPU, PPU, GPGPU, and/or variationsthereof. In at least one embodiment, a model optimizer generates aninternal representation of a model, and optimizes said model to generatean intermediate representation. In at least one embodiment, a modeloptimizer reduces a number of layers of a model. In at least oneembodiment, a model optimizer removes layers of a model that areutilized for training. In at least one embodiment, a model optimizerperforms various neural network operations, such as modifying inputs toa model (e.g., resizing inputs to a model), modifying a size of inputsof a model (e.g., modifying a batch size of a model), modifying a modelstructure (e.g., modifying layers of a model), normalization,standardization, quantization (e.g., converting weights of a model froma first representation, such as floating point, to a secondrepresentation, such as integer), and/or variations thereof.

In at least one embodiment, OpenVINO comprises one or more softwarelibraries for inferencing, also referred to as an inference engine. Inat least one embodiment, an inference engine is a C++ library, or anysuitable programming language library. In at least one embodiment, aninference engine is utilized to infer input data. In at least oneembodiment, an inference engine implements various classes to inferinput data and generate one or more results. In at least one embodiment,an inference engine implements one or more API functions to process anintermediate representation, set input and/or output formats, and/orexecute a model on one or more devices.

In at least one embodiment, OpenVINO provides various abilities forheterogeneous execution of one or more neural network models. In atleast one embodiment, heterogeneous execution, or heterogeneouscomputing, refers to one or more computing processes and/or systems thatutilize one or more types of processors and/or cores. In at least oneembodiment, OpenVINO provides various software functions to execute aprogram on one or more devices. In at least one embodiment, OpenVINOprovides various software functions to execute a program and/or portionsof a program on different devices. In at least one embodiment, OpenVINOprovides various software functions to, for example, run a first portionof code on a CPU and a second portion of code on a GPU and/or FPGA. Inat least one embodiment, OpenVINO provides various software functions toexecute one or more layers of a neural network on one or more devices(e.g., a first set of layers on a first device, such as a GPU, and asecond set of layers on a second device, such as a CPU).

In at least one embodiment, OpenVINO includes various functionalitysimilar to functionalities associated with a CUDA programming model,such as various neural network model operations associated withframeworks such as TensorFlow, PyTorch, and/or variations thereof. In atleast one embodiment, one or more CUDA programming model operations areperformed using OpenVINO. In at least one embodiment, various systems,methods, and/or techniques described herein are implemented usingOpenVINO.

Data Center

FIG. 8 illustrates an example data center 800, in which at least oneembodiment may be used. In at least one embodiment, data center 800includes a data center infrastructure layer 810, a framework layer 820,a software layer 830 and an application layer 840.

In at least one embodiment, as shown in FIG. 8 , data centerinfrastructure layer 810 may include a resource orchestrator 812,grouped computing resources 814, and node computing resources (“nodeC.R.s”) 816(1)-816(N), where “N” represents a positive integer (whichmay be a different integer “N” than used in other figures). In at leastone embodiment, node C.R.s 816(1)-816(N) may include, but are notlimited to, any number of central processing units (“CPUs”) or otherprocessors (including accelerators, field programmable gate arrays(FPGAs), graphics processors, etc.), memory storage devices818(1)-818(N) (e.g., dynamic read-only memory, solid state storage ordisk drives), network input/output (“NW I/O”) devices, network switches,virtual machines (“VMs”), power modules, and cooling modules, etc. In atleast one embodiment, one or more node C.R.s from among node C.R.s816(1)-816(N) may be a server having one or more of above-mentionedcomputing resources.

In at least one embodiment, grouped computing resources 814 may includeseparate groupings of node C.R.s housed within one or more racks (notshown), or many racks housed in data centers at various geographicallocations (also not shown). In at least one embodiment, separategroupings of node C.R.s within grouped computing resources 814 mayinclude grouped compute, network, memory or storage resources that maybe configured or allocated to support one or more workloads. In at leastone embodiment, several node C.R.s including CPUs or processors maygrouped within one or more racks to provide compute resources to supportone or more workloads. In at least one embodiment, one or more racks mayalso include any number of power modules, cooling modules, and networkswitches, in any combination.

In at least one embodiment, resource orchestrator 812 may configure orotherwise control one or more node C.R.s 816(1)-816(N) and/or groupedcomputing resources 814. In at least one embodiment, resourceorchestrator 812 may include a software design infrastructure (“SDI”)management entity for data center 800. In at least one embodiment,resource orchestrator 612 may include hardware, software or somecombination thereof.

In at least one embodiment, as shown in FIG. 8 , framework layer 820includes a job scheduler 822, a configuration manager 824, a resourcemanager 826 and a distributed file system 828. In at least oneembodiment, framework layer 820 may include a framework to supportsoftware 832 of software layer 830 and/or one or more application(s) 842of application layer 840. In at least one embodiment, software 832 orapplication(s) 842 may respectively include web-based service softwareor applications, such as those provided by Amazon Web Services, GoogleCloud and Microsoft Azure. In at least one embodiment, framework layer820 may be, but is not limited to, a type of free and open-sourcesoftware web application framework such as Apache Spark™ (hereinafter“Spark”) that may utilize distributed file system 828 for large-scaledata processing (e.g., “big data”). In at least one embodiment, jobscheduler 822 may include a Spark driver to facilitate scheduling ofworkloads supported by various layers of data center 800. In at leastone embodiment, configuration manager 824 may be capable of configuringdifferent layers such as software layer 830 and framework layer 820including Spark and distributed file system 828 for supportinglarge-scale data processing. In at least one embodiment, resourcemanager 826 may be capable of managing clustered or grouped computingresources mapped to or allocated for support of distributed file system828 and job scheduler 822. In at least one embodiment, clustered orgrouped computing resources may include grouped computing resources 814at data center infrastructure layer 810. In at least one embodiment,resource manager 826 may coordinate with resource orchestrator 812 tomanage these mapped or allocated computing resources.

In at least one embodiment, software 832 included in software layer 830may include software used by at least portions of node C.R.s816(1)-816(N), grouped computing resources 814, and/or distributed filesystem 828 of framework layer 820. In at least one embodiment, one ormore types of software may include, but are not limited to, Internet webpage search software, e-mail virus scan software, database software, andstreaming video content software.

In at least one embodiment, application(s) 842 included in applicationlayer 840 may include one or more types of applications used by at leastportions of node C.R.s 816(1)-816(N), grouped computing resources 814,and/or distributed file system 828 of framework layer 820. In at leastone embodiment, one or more types of applications may include, but arenot limited to, any number of a genomics application, a cognitivecompute, application and a machine learning application, includingtraining or inferencing software, machine learning framework software(e.g., PyTorch, TensorFlow, Caffe, etc.) or other machine learningapplications used in conjunction with one or more embodiments.

In at least one embodiment, any of configuration manager 824, resourcemanager 826, and resource orchestrator 812 may implement any number andtype of self-modifying actions based on any amount and type of dataacquired in any technically feasible fashion. In at least oneembodiment, self-modifying actions may relieve a data center operator ofdata center 800 from making possibly bad configuration decisions andpossibly avoiding underutilized and/or poor performing portions of adata center.

In at least one embodiment, data center 800 may include tools, services,software or other resources to train one or more machine learning modelsor predict or infer information using one or more machine learningmodels according to one or more embodiments described herein. Forexample, in at least one embodiment, a machine learning model may betrained by calculating weight parameters according to a neural networkarchitecture using software and computing resources described above withrespect to data center 800. In at least one embodiment, trained machinelearning models corresponding to one or more neural networks may be usedto infer or predict information using resources described above withrespect to data center 800 by using weight parameters calculated throughone or more training techniques described herein.

In at least one embodiment, data center may use CPUs,application-specific integrated circuits (ASICs), GPUs, FPGAs, or otherhardware to perform training and/or inferencing using above-describedresources. Moreover, one or more software and/or hardware resourcesdescribed above may be configured as a service to allow users to trainor performing inferencing of information, such as image recognition,speech recognition, or other artificial intelligence services.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in systemFIG. 8 for inferencing or predicting operations based, at least in part,on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the system ofFIG. 8 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

Computer Systems

FIG. 9 is a block diagram illustrating an exemplary computer system,which may be a system with interconnected devices and components, asystem-on-a-chip (SOC) or some combination thereof formed with aprocessor that may include execution units to execute an instruction,according to at least one embodiment. In at least one embodiment, acomputer system 900 may include, without limitation, a component, suchas a processor 902 to employ execution units including logic to performalgorithms for process data, in accordance with present disclosure, suchas in embodiment described herein. In at least one embodiment, computersystem 900 may include processors, such as PENTIUM® Processor family,Xeon™ Itanium®, XScale™ and/or StrongARM™, Intel® Core™, or Intel®Nervana™ microprocessors available from Intel Corporation of SantaClara, California, although other systems (including PCs having othermicroprocessors, engineering workstations, set-top boxes and like) mayalso be used. In at least one embodiment, computer system 900 mayexecute a version of WINDOWS operating system available from MicrosoftCorporation of Redmond, Wash., although other operating systems (UNIXand Linux, for example), embedded software, and/or graphical userinterfaces, may also be used.

Embodiments may be used in other devices such as handheld devices andembedded applications. Some examples of handheld devices includecellular phones, Internet Protocol devices, digital cameras, personaldigital assistants (“PDAs”), and handheld PCs. In at least oneembodiment, embedded applications may include a microcontroller, adigital signal processor (“DSP”), system on a chip, network computers(“NetPCs”), set-top boxes, network hubs, wide area network (“WAN”)switches, or any other system that may perform one or more instructionsin accordance with at least one embodiment.

In at least one embodiment, computer system 900 may include, withoutlimitation, processor 902 that may include, without limitation, one ormore execution units 908 to perform machine learning model trainingand/or inferencing according to techniques described herein. In at leastone embodiment, computer system 900 is a single processor desktop orserver system, but in another embodiment, computer system 900 may be amultiprocessor system. In at least one embodiment, processor 902 mayinclude, without limitation, a complex instruction set computer (“CISC”)microprocessor, a reduced instruction set computing (“RISC”)microprocessor, a very long instruction word (“VLIW”) microprocessor, aprocessor implementing a combination of instruction sets, or any otherprocessor device, such as a digital signal processor, for example. In atleast one embodiment, processor 902 may be coupled to a processor bus910 that may transmit data signals between processor 902 and othercomponents in computer system 900.

In at least one embodiment, processor 902 may include, withoutlimitation, a Level 1 (“L1”) internal cache memory (“cache”) 904. In atleast one embodiment, processor 902 may have a single internal cache ormultiple levels of internal cache. In at least one embodiment, cachememory may reside external to processor 902. Other embodiments may alsoinclude a combination of both internal and external caches depending onparticular implementation and needs. In at least one embodiment, aregister file 906 may store different types of data in various registersincluding, without limitation, integer registers, floating pointregisters, status registers, and an instruction pointer register.

In at least one embodiment, execution unit 908, including, withoutlimitation, logic to perform integer and floating point operations, alsoresides in processor 902. In at least one embodiment, processor 902 mayalso include a microcode (“ucode”) read only memory (“ROM”) that storesmicrocode for certain macro instructions. In at least one embodiment,execution unit 908 may include logic to handle a packed instruction set909. In at least one embodiment, by including packed instruction set 909in an instruction set of a general-purpose processor, along withassociated circuitry to execute instructions, operations used by manymultimedia applications may be performed using packed data in processor902. In at least one embodiment, many multimedia applications may beaccelerated and executed more efficiently by using a full width of aprocessor's data bus for performing operations on packed data, which mayeliminate a need to transfer smaller units of data across thatprocessor's data bus to perform one or more operations one data elementat a time.

In at least one embodiment, execution unit 908 may also be used inmicrocontrollers, embedded processors, graphics devices, DSPs, and othertypes of logic circuits. In at least one embodiment, computer system 900may include, without limitation, a memory 920. In at least oneembodiment, memory 920 may be a Dynamic Random Access Memory (“DRAM”)device, a Static Random Access Memory (“SRAM”) device, a flash memorydevice, or another memory device. In at least one embodiment, memory 920may store instruction(s) 919 and/or data 921 represented by data signalsthat may be executed by processor 902.

In at least one embodiment, a system logic chip may be coupled toprocessor bus 910 and memory 920. In at least one embodiment, a systemlogic chip may include, without limitation, a memory controller hub(“MCH”) 916, and processor 902 may communicate with MCH 916 viaprocessor bus 910. In at least one embodiment, MCH 916 may provide ahigh bandwidth memory path 918 to memory 920 for instruction and datastorage and for storage of graphics commands, data and textures. In atleast one embodiment, MCH 916 may direct data signals between processor902, memory 920, and other components in computer system 900 and tobridge data signals between processor bus 910, memory 920, and a systemI/O interface 922. In at least one embodiment, a system logic chip mayprovide a graphics port for coupling to a graphics controller. In atleast one embodiment, MCH 916 may be coupled to memory 920 through highbandwidth memory path 918 and a graphics/video card 912 may be coupledto MCH 916 through an Accelerated Graphics Port (“AGP”) interconnect914.

In at least one embodiment, computer system 900 may use system I/Ointerface 922 as a proprietary hub interface bus to couple MCH 916 to anI/O controller hub (“ICH”) 930. In at least one embodiment, ICH 930 mayprovide direct connections to some I/O devices via a local I/O bus. Inat least one embodiment, a local I/O bus may include, withoutlimitation, a high-speed I/O bus for connecting peripherals to memory920, a chipset, and processor 902. Examples may include, withoutlimitation, an audio controller 929, a firmware hub (“flash BIOS”) 928,a wireless transceiver 926, a data storage 924, a legacy I/O controller923 containing user input and keyboard interfaces 925, a serialexpansion port 927, such as a Universal Serial Bus (“USB”) port, and anetwork controller 934. In at least one embodiment, data storage 924 maycomprise a hard disk drive, a floppy disk drive, a CD-ROM device, aflash memory device, or other mass storage device.

In at least one embodiment, FIG. 9 illustrates a system, which includesinterconnected hardware devices or “chips”, whereas in otherembodiments, FIG. 9 may illustrate an exemplary SoC. In at least oneembodiment, devices illustrated in FIG. 9 may be interconnected withproprietary interconnects, standardized interconnects (e.g., PCIe) orsome combination thereof. In at least one embodiment, one or morecomponents of computer system 900 are interconnected using computeexpress link (CXL) interconnects.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in systemFIG. 9 for inferencing or predicting operations based, at least in part,on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 9 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 10 is a block diagram illustrating an electronic device 1000 forutilizing a processor 1010, according to at least one embodiment. In atleast one embodiment, electronic device 1000 may be, for example andwithout limitation, a notebook, a tower server, a rack server, a bladeserver, a laptop, a desktop, a tablet, a mobile device, a phone, anembedded computer, or any other suitable electronic device.

In at least one embodiment, electronic device 1000 may include, withoutlimitation, processor 1010 communicatively coupled to any suitablenumber or kind of components, peripherals, modules, or devices. In atleast one embodiment, processor 1010 is coupled using a bus orinterface, such as a I²C bus, a System Management Bus (“SMBus”), a LowPin Count (LPC) bus, a Serial Peripheral Interface (“SPI”), a HighDefinition Audio (“HDA”) bus, a Serial Advance Technology Attachment(“SATA”) bus, a Universal Serial Bus (“USB”) (versions 1, 2, 3, etc.),or a Universal Asynchronous Receiver/Transmitter (“UART”) bus. In atleast one embodiment, FIG. 10 illustrates a system, which includesinterconnected hardware devices or “chips”, whereas in otherembodiments, FIG. 10 may illustrate an exemplary SoC. In at least oneembodiment, devices illustrated in FIG. 10 may be interconnected withproprietary interconnects, standardized interconnects (e.g., PCIe) orsome combination thereof. In at least one embodiment, one or morecomponents of FIG. 10 are interconnected using compute express link(CXL) interconnects.

In at least one embodiment, FIG. 10 may include a display 1024, a touchscreen 1025, a touch pad 1030, a Near Field Communications unit (“NFC”)1045, a sensor hub 1040, a thermal sensor 1046, an Express Chipset(“EC”) 1035, a Trusted Platform Module (“TPM”) 1038, BIOS/firmware/flashmemory (“BIOS, FW Flash”) 1022, a DSP 1060, a drive 1020 such as a SolidState Disk (“SSD”) or a Hard Disk Drive (“HDD”), a wireless local areanetwork unit (“WLAN”) 1050, a Bluetooth unit 1052, a Wireless Wide AreaNetwork unit (“WWAN”) 1056, a Global Positioning System (GPS) unit 1055,a camera (“USB 3.0 camera”) 1054 such as a USB 3.0 camera, and/or a LowPower Double Data Rate (“LPDDR”) memory unit (“LPDDR3”) 1015 implementedin, for example, an LPDDR3 standard. These components may each beimplemented in any suitable manner.

In at least one embodiment, other components may be communicativelycoupled to processor 1010 through components described herein. In atleast one embodiment, an accelerometer 1041, an ambient light sensor(“ALS”) 1042, a compass 1043, and a gyroscope 1044 may becommunicatively coupled to sensor hub 1040. In at least one embodiment,a thermal sensor 1039, a fan 1037, a keyboard 1036, and touch pad 1030may be communicatively coupled to EC 1035. In at least one embodiment,speakers 1063, headphones 1064, and a microphone (“mic”) 1065 may becommunicatively coupled to an audio unit (“audio codec and class D amp”)1062, which may in turn be communicatively coupled to DSP 1060. In atleast one embodiment, audio unit 1062 may include, for example andwithout limitation, an audio coder/decoder (“codec”) and a class Damplifier. In at least one embodiment, a SIM card (“SIM”) 1057 may becommunicatively coupled to WWAN unit 1056. In at least one embodiment,components such as WLAN unit 1050 and Bluetooth unit 1052, as well asWWAN unit 1056 may be implemented in a Next Generation Form Factor(“NGFF”).

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in systemFIG. 10 for inferencing or predicting operations based, at least inpart, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 10 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 11 illustrates a computer system 1100, according to at least oneembodiment. In at least one embodiment, computer system 1100 isconfigured to implement various processes and methods describedthroughout this disclosure.

In at least one embodiment, computer system 1100 comprises, withoutlimitation, at least one central processing unit (“CPU”) 1102 that isconnected to a communication bus 1110 implemented using any suitableprotocol, such as PCI (“Peripheral Component Interconnect”), peripheralcomponent interconnect express (“PCI-Express”), AGP (“AcceleratedGraphics Port”), HyperTransport, or any other bus or point-to-pointcommunication protocol(s). In at least one embodiment, computer system1100 includes, without limitation, a main memory 1104 and control logic(e.g., implemented as hardware, software, or a combination thereof) anddata are stored in main memory 1104, which may take form of randomaccess memory (“RAM”). In at least one embodiment, a network interfacesubsystem (“network interface”) 1122 provides an interface to othercomputing devices and networks for receiving data from and transmittingdata to other systems with computer system 1100.

In at least one embodiment, computer system 1100, in at least oneembodiment, includes, without limitation, input devices 1108, a parallelprocessing system 1112, and display devices 1106 that can be implementedusing a conventional cathode ray tube (“CRT”), a liquid crystal display(“LCD”), a light emitting diode (“LED”) display, a plasma display, orother suitable display technologies. In at least one embodiment, userinput is received from input devices 1108 such as keyboard, mouse,touchpad, microphone, etc. In at least one embodiment, each moduledescribed herein can be situated on a single semiconductor platform toform a processing system.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in systemFIG. 11 for inferencing or predicting operations based, at least inpart, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 11 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 12 illustrates a computer system 1200, according to at least oneembodiment. In at least one embodiment, computer system 1200 includes,without limitation, a computer 1210 and a USB stick 1220. In at leastone embodiment, computer 1210 may include, without limitation, anynumber and type of processor(s) (not shown) and a memory (not shown). Inat least one embodiment, computer 1210 includes, without limitation, aserver, a cloud instance, a laptop, and a desktop computer.

In at least one embodiment, USB stick 1220 includes, without limitation,a processing unit 1230, a USB interface 1240, and USB interface logic1250. In at least one embodiment, processing unit 1230 may be anyinstruction execution system, apparatus, or device capable of executinginstructions. In at least one embodiment, processing unit 1230 mayinclude, without limitation, any number and type of processing cores(not shown). In at least one embodiment, processing unit 1230 comprisesan application specific integrated circuit (“ASIC”) that is optimized toperform any amount and type of operations associated with machinelearning. For instance, in at least one embodiment, processing unit 1230is a tensor processing unit (“TPC”) that is optimized to perform machinelearning inference operations. In at least one embodiment, processingunit 1230 is a vision processing unit (“VPU”) that is optimized toperform machine vision and machine learning inference operations.

In at least one embodiment, USB interface 1240 may be any type of USBconnector or USB socket. For instance, in at least one embodiment, USBinterface 1240 is a USB 3.0 Type-C socket for data and power. In atleast one embodiment, USB interface 1240 is a USB 3.0 Type-A connector.In at least one embodiment, USB interface logic 1250 may include anyamount and type of logic that enables processing unit 1230 to interfacewith devices (e.g., computer 1210) via USB connector 1240.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in systemFIG. 12 for inferencing or predicting operations based, at least inpart, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 12 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 13A illustrates an exemplary architecture in which a plurality ofGPUs 1310(1)-1310(N) is communicatively coupled to a plurality ofmulti-core processors 1305(1)-1305(M) over high-speed links1340(1)-1340(N) (e.g., buses, point-to-point interconnects, etc.). In atleast one embodiment, high-speed links 1340(1)-1340(N) support acommunication throughput of 4 GB/s, 30 GB/s, 80 GB/s or higher. In atleast one embodiment, various interconnect protocols may be usedincluding, but not limited to, PCIe 4.0 or 5.0 and NVLink 2.0. Invarious figures, “N” and “M” represent positive integers, values ofwhich may be different from FIG. to figure. In at least one embodiment,one or more GPUs in a plurality of GPUs 1310(1)-1310(N) includes one ormore graphics cores (also referred to simply as “cores”) 1600 asdisclosed in FIGS. 16A and 16B. In at least one embodiment, one or moregraphics cores 1600 may be referred to as streaming multiprocessors(“SMs”), stream processors (“SPs”), stream processing units (“SPUs”),compute units (“CUs”), execution units (“EUs”), and/or slices, where aslice in this context can refer to a portion of processing resources ina processing unit (e.g., 16 cores, a ray tracing unit, a thread directoror scheduler).

In addition, and in at least one embodiment, two or more of GPUs 1310are interconnected over high-speed links 1329(1)-1329(2), which may beimplemented using similar or different protocols/links than those usedfor high-speed links 1340(1)-1340(N). Similarly, two or more ofmulti-core processors 1305 may be connected over a high-speed link 1328which may be symmetric multi-processor (SMP) buses operating at 20 GB/s,30 GB/s, 120 GB/s or higher. Alternatively, all communication betweenvarious system components shown in FIG. 13A may be accomplished usingsimilar protocols/links (e.g., over a common interconnection fabric).

In at least one embodiment, each multi-core processor 1305 iscommunicatively coupled to a processor memory 1301(1)-1301(M), viamemory interconnects 1326(1)-1326(M), respectively, and each GPU1310(1)-1310(N) is communicatively coupled to GPU memory 1320(1)-1320(N)over GPU memory interconnects 1350(1)-1350(N), respectively. In at leastone embodiment, memory interconnects 1326 and 1350 may utilize similaror different memory access technologies. By way of example, and notlimitation, processor memories 1301(1)-1301(M) and GPU memories 1320 maybe volatile memories such as dynamic random access memories (DRAMs)(including stacked DRAMs), Graphics DDR SDRAM (GDDR) (e.g., GDDR5,GDDR6), or High Bandwidth Memory (HBM) and/or may be non-volatilememories such as 3D)(Point or Nano-Ram. In at least one embodiment, someportion of processor memories 1301 may be volatile memory and anotherportion may be non-volatile memory (e.g., using a two-level memory (2LM)hierarchy).

As described herein, although various multi-core processors 1305 andGPUs 1310 may be physically coupled to a particular memory 1301, 1320,respectively, and/or a unified memory architecture may be implemented inwhich a virtual system address space (also referred to as “effectiveaddress” space) is distributed among various physical memories. Forexample, processor memories 1301(1)-1301(M) may each comprise 64 GB ofsystem memory address space and GPU memories 1320(1)-1320(N) may eachcomprise 32 GB of system memory address space resulting in a total of256 GB addressable memory when M=2 and N=4. Other values for N and M arepossible.

FIG. 13B illustrates additional details for an interconnection between amulti-core processor 1307 and a graphics acceleration module 1346 inaccordance with one exemplary embodiment. In at least one embodiment,graphics acceleration module 1346 may include one or more GPU chipsintegrated on a line card which is coupled to processor 1307 viahigh-speed link 1340 (e.g., a PCIe bus, NVLink, etc.). In at least oneembodiment, graphics acceleration module 1346 may alternatively beintegrated on a package or chip with processor 1307.

In at least one embodiment, processor 1307 includes a plurality of cores1360A-1360D (which may be referred to as “execution units”), each with atranslation lookaside buffer (“TLB”) 1361A-1361D and one or more caches1362A-1362D. In at least one embodiment, cores 1360A-1360D may includevarious other components for executing instructions and processing datathat are not illustrated. In at least one embodiment, caches 1362A-1362Dmay comprise Level 1 (L1) and Level 2 (L2) caches. In addition, one ormore shared caches 1356 may be included in caches 1362A-1362D and sharedby sets of cores 1360A-1360D. For example, one embodiment of processor1307 includes 24 cores, each with its own L1 cache, twelve shared L2caches, and twelve shared L3 caches. In this embodiment, one or more L2and L3 caches are shared by two adjacent cores. In at least oneembodiment, processor 1307 and graphics acceleration module 1346 connectwith system memory 1314, which may include processor memories1301(1)-1301(M) of FIG. 13A.

In at least one embodiment, coherency is maintained for data andinstructions stored in various caches 1362A-1362D, 1356 and systemmemory 1314 via inter-core communication over a coherence bus 1364. Inat least one embodiment, for example, each cache may have cachecoherency logic/circuitry associated therewith to communicate to overcoherence bus 1364 in response to detected reads or writes to particularcache lines. In at least one embodiment, a cache snooping protocol isimplemented over coherence bus 1364 to snoop cache accesses.

In at least one embodiment, a proxy circuit 1325 communicatively couplesgraphics acceleration module 1346 to coherence bus 1364, allowinggraphics acceleration module 1346 to participate in a cache coherenceprotocol as a peer of cores 1360A-1360D. In particular, in at least oneembodiment, an interface 1335 provides connectivity to proxy circuit1325 over high-speed link 1340 and an interface 1337 connects graphicsacceleration module 1346 to high-speed link 1340.

In at least one embodiment, an accelerator integration circuit 1336provides cache management, memory access, context management, andinterrupt management services on behalf of a plurality of graphicsprocessing engines 1331(1)-1331(N) of graphics acceleration module 1346.In at least one embodiment, graphics processing engines 1331(1)-1331(N)may each comprise a separate graphics processing unit (GPU). In at leastone embodiment, plurality of graphics processing engines 1331(1)-1331(N)of graphics acceleration module 1346 include one or more graphics cores1600 as discussed in connection with FIGS. 16A and 16B. In at least oneembodiment, graphics processing engines 1331(1)-1331(N) alternativelymay comprise different types of graphics processing engines within aGPU, such as graphics execution units, media processing engines (e.g.,video encoders/decoders), samplers, and blit engines. In at least oneembodiment, graphics acceleration module 1346 may be a GPU with aplurality of graphics processing engines 1331(1)-1331(N) or graphicsprocessing engines 1331(1)-1331(N) may be individual GPUs integrated ona common package, line card, or chip.

In at least one embodiment, accelerator integration circuit 1336includes a memory management unit (MMU) 1339 for performing variousmemory management functions such as virtual-to-physical memorytranslations (also referred to as effective-to-real memory translations)and memory access protocols for accessing system memory 1314. In atleast one embodiment, MMU 1339 may also include a translation lookasidebuffer (TLB) (not shown) for caching virtual/effective to physical/realaddress translations. In at least one embodiment, a cache 1338 can storecommands and data for efficient access by graphics processing engines1331(1)-1331(N). In at least one embodiment, data stored in cache 1338and graphics memories 1333(1)-1333(M) is kept coherent with core caches1362A-1362D, 1356 and system memory 1314, possibly using a fetch unit1344. As mentioned, this may be accomplished via proxy circuit 1325 onbehalf of cache 1338 and memories 1333(1)-1333(M) (e.g., sending updatesto cache 1338 related to modifications/accesses of cache lines onprocessor caches 1362A-1362D, 1356 and receiving updates from cache1338).

In at least one embodiment, a set of registers 1345 store context datafor threads executed by graphics processing engines 1331(1)-1331(N) anda context management circuit 1348 manages thread contexts. For example,context management circuit 1348 may perform save and restore operationsto save and restore contexts of various threads during contexts switches(e.g., where a first thread is saved and a second thread is stored sothat a second thread can be execute by a graphics processing engine).For example, on a context switch, context management circuit 1348 maystore current register values to a designated region in memory (e.g.,identified by a context pointer). It may then restore register valueswhen returning to a context. In at least one embodiment, an interruptmanagement circuit 1347 receives and processes interrupts received fromsystem devices.

In at least one embodiment, virtual/effective addresses from a graphicsprocessing engine 1331 are translated to real/physical addresses insystem memory 1314 by MMU 1339. In at least one embodiment, acceleratorintegration circuit 1336 supports multiple (e.g., 4, 8, 16) graphicsaccelerator modules 1346 and/or other accelerator devices. In at leastone embodiment, graphics accelerator module 1346 may be dedicated to asingle application executed on processor 1307 or may be shared betweenmultiple applications. In at least one embodiment, a virtualizedgraphics execution environment is presented in which resources ofgraphics processing engines 1331(1)-1331(N) are shared with multipleapplications or virtual machines (VMs). In at least one embodiment,resources may be subdivided into “slices” which are allocated todifferent VMs and/or applications based on processing requirements andpriorities associated with VMs and/or applications.

In at least one embodiment, accelerator integration circuit 1336performs as a bridge to a system for graphics acceleration module 1346and provides address translation and system memory cache services. Inaddition, in at least one embodiment, accelerator integration circuit1336 may provide virtualization facilities for a host processor tomanage virtualization of graphics processing engines 1331(1)-1331(N),interrupts, and memory management.

In at least one embodiment, because hardware resources of graphicsprocessing engines 1331(1)-1331(N) are mapped explicitly to a realaddress space seen by host processor 1307, any host processor canaddress these resources directly using an effective address value. In atleast one embodiment, one function of accelerator integration circuit1336 is physical separation of graphics processing engines1331(1)-1331(N) so that they appear to a system as independent units.

In at least one embodiment, one or more graphics memories1333(1)-1333(M) are coupled to each of graphics processing engines1331(1)-1331(N), respectively and N=M. In at least one embodiment,graphics memories 1333(1)-1333(M) store instructions and data beingprocessed by each of graphics processing engines 1331(1)-1331(N). In atleast one embodiment, graphics memories 1333(1)-1333(M) may be volatilememories such as DRAMs (including stacked DRAMs), GDDR memory (e.g.,GDDR5, GDDR6), or HBM, and/or may be non-volatile memories such as 3DXPoint or Nano-Ram.

In at least one embodiment, to reduce data traffic over high-speed link1340, biasing techniques can be used to ensure that data stored ingraphics memories 1333(1)-1333(M) is data that will be used mostfrequently by graphics processing engines 1331(1)-1331(N) and preferablynot used by cores 1360A-1360D (at least not frequently). Similarly, inat least one embodiment, a biasing mechanism attempts to keep dataneeded by cores (and preferably not graphics processing engines1331(1)-1331(N)) within caches 1362A-1362D, 1356 and system memory 1314.

FIG. 13C illustrates another exemplary embodiment in which acceleratorintegration circuit 1336 is integrated within processor 1307. In thisembodiment, graphics processing engines 1331(1)-1331(N) communicatedirectly over high-speed link 1340 to accelerator integration circuit1336 via interface 1337 and interface 1335 (which, again, may be anyform of bus or interface protocol). In at least one embodiment,accelerator integration circuit 1336 may perform similar operations asthose described with respect to FIG. 13B, but potentially at a higherthroughput given its close proximity to coherence bus 1364 and caches1362A-1362D, 1356. In at least one embodiment, an acceleratorintegration circuit supports different programming models including adedicated-process programming model (no graphics acceleration modulevirtualization) and shared programming models (with virtualization),which may include programming models which are controlled by acceleratorintegration circuit 1336 and programming models which are controlled bygraphics acceleration module 1346.

In at least one embodiment, graphics processing engines 1331(1)-1331(N)are dedicated to a single application or process under a singleoperating system. In at least one embodiment, a single application canfunnel other application requests to graphics processing engines1331(1)-1331(N), providing virtualization within a VM/partition.

In at least one embodiment, graphics processing engines 1331(1)-1331(N),may be shared by multiple VM/application partitions. In at least oneembodiment, shared models may use a system hypervisor to virtualizegraphics processing engines 1331(1)-1331(N) to allow access by eachoperating system. In at least one embodiment, for single-partitionsystems without a hypervisor, graphics processing engines1331(1)-1331(N) are owned by an operating system. In at least oneembodiment, an operating system can virtualize graphics processingengines 1331(1)-1331(N) to provide access to each process orapplication.

In at least one embodiment, graphics acceleration module 1346 or anindividual graphics processing engine 1331(1)-1331(N) selects a processelement using a process handle. In at least one embodiment, processelements are stored in system memory 1314 and are addressable using aneffective address to real address translation technique describedherein. In at least one embodiment, a process handle may be animplementation-specific value provided to a host process whenregistering its context with graphics processing engine 1331(1)-1331(N)(that is, calling system software to add a process element to a processelement linked list). In at least one embodiment, a lower 16-bits of aprocess handle may be an offset of a process element within a processelement linked list.

FIG. 13D illustrates an exemplary accelerator integration slice 1390. Inat least one embodiment, a “slice” comprises a specified portion ofprocessing resources of accelerator integration circuit 1336. In atleast one embodiment, an application is effective address space 1382within system memory 1314 stores process elements 1383. In at least oneembodiment, process elements 1383 are stored in response to GPUinvocations 1381 from applications 1380 executed on processor 1307. Inat least one embodiment, a process element 1383 contains process statefor corresponding application 1380. In at least one embodiment, a workdescriptor (WD) 1384 contained in process element 1383 can be a singlejob requested by an application or may contain a pointer to a queue ofjobs. In at least one embodiment, WD 1384 is a pointer to a job requestqueue in an application's effective address space 1382.

In at least one embodiment, graphics acceleration module 1346 and/orindividual graphics processing engines 1331(1)-1331(N) can be shared byall or a subset of processes in a system. In at least one embodiment, aninfrastructure for setting up process states and sending a WD 1384 to agraphics acceleration module 1346 to start a job in a virtualizedenvironment may be included.

In at least one embodiment, a dedicated-process programming model isimplementation-specific. In at least one embodiment, in this model, asingle process owns graphics acceleration module 1346 or an individualgraphics processing engine 1331. In at least one embodiment, whengraphics acceleration module 1346 is owned by a single process, ahypervisor initializes accelerator integration circuit 1336 for anowning partition and an operating system initializes acceleratorintegration circuit 1336 for an owning process when graphicsacceleration module 1346 is assigned.

In at least one embodiment, in operation, a WD fetch unit 1391 inaccelerator integration slice 1390 fetches next WD 1384, which includesan indication of work to be done by one or more graphics processingengines of graphics acceleration module 1346. In at least oneembodiment, data from WD 1384 may be stored in registers 1345 and usedby MMU 1339, interrupt management circuit 1347 and/or context managementcircuit 1348 as illustrated. For example, one embodiment of MMU 1339includes segment/page walk circuitry for accessing segment/page tables1386 within an OS virtual address space 1385. In at least oneembodiment, interrupt management circuit 1347 may process interruptevents 1392 received from graphics acceleration module 1346. In at leastone embodiment, when performing graphics operations, an effectiveaddress 1393 generated by a graphics processing engine 1331(1)-1331(N)is translated to a real address by MMU 1339.

In at least one embodiment, registers 1345 are duplicated for eachgraphics processing engine 1331(1)-1331(N) and/or graphics accelerationmodule 1346 and may be initialized by a hypervisor or an operatingsystem. In at least one embodiment, each of these duplicated registersmay be included in an accelerator integration slice 1390. Exemplaryregisters that may be initialized by a hypervisor are shown in Table 1.

TABLE 1 Hypervisor Initialized Registers Register # Description 1 SliceControl Register 2 Real Address (RA) Scheduled Processes Area Pointer 3Authority Mask Override Register 4 Interrupt Vector Table Entry Offset 5Interrupt Vector Table Entry Limit 6 State Register 7 Logical PartitionID 8 Real address (RA) Hypervisor Accelerator Utilization Record Pointer9 Storage Description Register

Exemplary registers that may be initialized by an operating system areshown in Table 2.

TABLE 2 Operating System Initialized Registers Register # Description 1Process and Thread Identification 2 Effective Address (EA) ContextSave/Restore Pointer 3 Virtual Address (VA) Accelerator UtilizationRecord Pointer 4 Virtual Address (VA) Storage Segment Table Pointer 5Authority Mask 6 Work descriptor

In at least one embodiment, each WD 1384 is specific to a particulargraphics acceleration module 1346 and/or graphics processing engines1331(1)-1331(N). In at least one embodiment, it contains all informationrequired by a graphics processing engine 1331(1)-1331(N) to do work, orit can be a pointer to a memory location where an application has set upa command queue of work to be completed.

FIG. 13E illustrates additional details for one exemplary embodiment ofa shared model. This embodiment includes a hypervisor real address space1398 in which a process element list 1399 is stored. In at least oneembodiment, hypervisor real address space 1398 is accessible via ahypervisor 1396 which virtualizes graphics acceleration module enginesfor operating system 1395.

In at least one embodiment, shared programming models allow for all or asubset of processes from all or a subset of partitions in a system touse a graphics acceleration module 1346. In at least one embodiment,there are two programming models where graphics acceleration module 1346is shared by multiple processes and partitions, namely time-slicedshared and graphics directed shared.

In at least one embodiment, in this model, system hypervisor 1396 ownsgraphics acceleration module 1346 and makes its function available toall operating systems 1395. In at least one embodiment, for a graphicsacceleration module 1346 to support virtualization by system hypervisor1396, graphics acceleration module 1346 may adhere to certainrequirements, such as (1) an application's job request must beautonomous (that is, state does not need to be maintained between jobs),or graphics acceleration module 1346 must provide a context save andrestore mechanism, (2) an application's job request is guaranteed bygraphics acceleration module 1346 to complete in a specified amount oftime, including any translation faults, or graphics acceleration module1346 provides an ability to preempt processing of a job, and (3)graphics acceleration module 1346 must be guaranteed fairness betweenprocesses when operating in a directed shared programming model.

In at least one embodiment, application 1380 is required to make anoperating system 1395 system call with a graphics acceleration moduletype, a work descriptor (WD), an authority mask register (AMR) value,and a context save/restore area pointer (CSRP). In at least oneembodiment, graphics acceleration module type describes a targetedacceleration function for a system call. In at least one embodiment,graphics acceleration module type may be a system-specific value. In atleast one embodiment, WD is formatted specifically for graphicsacceleration module 1346 and can be in a form of a graphics accelerationmodule 1346 command, an effective address pointer to a user-definedstructure, an effective address pointer to a queue of commands, or anyother data structure to describe work to be done by graphicsacceleration module 1346.

In at least one embodiment, an AMR value is an AMR state to use for acurrent process. In at least one embodiment, a value passed to anoperating system is similar to an application setting an AMR. In atleast one embodiment, if accelerator integration circuit 1336 (notshown) and graphics acceleration module 1346 implementations do notsupport a User Authority Mask Override Register (UAMOR), an operatingsystem may apply a current UAMOR value to an AMR value before passing anAMR in a hypervisor call. In at least one embodiment, hypervisor 1396may optionally apply a current Authority Mask Override Register (AMOR)value before placing an AMR into process element 1383. In at least oneembodiment, CSRP is one of registers 1345 containing an effectiveaddress of an area in an application's effective address space 1382 forgraphics acceleration module 1346 to save and restore context state. Inat least one embodiment, this pointer is optional if no state isrequired to be saved between jobs or when a job is preempted. In atleast one embodiment, context save/restore area may be pinned systemmemory.

Upon receiving a system call, operating system 1395 may verify thatapplication 1380 has registered and been given authority to use graphicsacceleration module 1346. In at least one embodiment, operating system1395 then calls hypervisor 1396 with information shown in Table 3.

TABLE 3 OS to Hypervisor Call Parameters Parameter # Description 1 Awork descriptor (WD) 2 An Authority Mask Register (AMR) value(potentially masked) 3 An effective address (EA) Context Save/RestoreArea Pointer (CSRP) 4 A process ID (PID) and optional thread ID (TID) 5A virtual address (VA) accelerator utilization record pointer (AURP) 6Virtual address of storage segment table pointer (SSTP) 7 A logicalinterrupt service number (LISN)

In at least one embodiment, upon receiving a hypervisor call, hypervisor1396 verifies that operating system 1395 has registered and been givenauthority to use graphics acceleration module 1346. In at least oneembodiment, hypervisor 1396 then puts process element 1383 into aprocess element linked list for a corresponding graphics accelerationmodule 1346 type. In at least one embodiment, a process element mayinclude information shown in Table 4.

TABLE 4 Process Element Information Element # Description 1 A workdescriptor (WD) 2 An Authority Mask Register (AMR) value (potentiallymasked). 3 An effective address (EA) Context Save/Restore Area Pointer(CSRP) 4 A process ID (PID) and optional thread ID (TID) 5 A virtualaddress (VA) accelerator utilization record pointer (AURP) 6 Virtualaddress of storage segment table pointer (SSTP) 7 A logical interruptservice number (LISN) 8 Interrupt vector table, derived from hypervisorcall parameters 9 A state register (SR) value 10 A logical partition ID(LPID) 11 A real address (RA) hypervisor accelerator utilization recordpointer 12 Storage Descriptor Register (SDR)

In at least one embodiment, hypervisor initializes a plurality ofaccelerator integration slice 1390 registers 1345.

As illustrated in FIG. 13F, in at least one embodiment, a unified memoryis used, addressable via a common virtual memory address space used toaccess physical processor memories 1301(1)-1301(N) and GPU memories1320(1)-1320(N). In this implementation, operations executed on GPUs1310(1)-1310(N) utilize a same virtual/effective memory address space toaccess processor memories 1301(1)-1301(M) and vice versa, therebysimplifying programmability. In at least one embodiment, a first portionof a virtual/effective address space is allocated to processor memory1301(1), a second portion to second processor memory 1301(N), a thirdportion to GPU memory 1320(1), and so on. In at least one embodiment, anentire virtual/effective memory space (sometimes referred to as aneffective address space) is thereby distributed across each of processormemories 1301 and GPU memories 1320, allowing any processor or GPU toaccess any physical memory with a virtual address mapped to that memory.

In at least one embodiment, bias/coherence management circuitry1394A-1394E within one or more of MMUs 1339A-1339E ensures cachecoherence between caches of one or more host processors (e.g., 1305) andGPUs 1310 and implements biasing techniques indicating physical memoriesin which certain types of data should be stored. In at least oneembodiment, while multiple instances of bias/coherence managementcircuitry 1394A-1394E are illustrated in FIG. 13F, bias/coherencecircuitry may be implemented within an MMU of one or more hostprocessors 1305 and/or within accelerator integration circuit 1336.

One embodiment allows GPU memories 1320 to be mapped as part of systemmemory, and accessed using shared virtual memory (SVM) technology, butwithout suffering performance drawbacks associated with full systemcache coherence. In at least one embodiment, an ability for GPU memories1320 to be accessed as system memory without onerous cache coherenceoverhead provides a beneficial operating environment for GPU offload. Inat least one embodiment, this arrangement allows software of hostprocessor 1305 to setup operands and access computation results, withoutoverhead of tradition I/O DMA data copies. In at least one embodiment,such traditional copies involve driver calls, interrupts and memorymapped I/O (MMIO) accesses that are all inefficient relative to simplememory accesses. In at least one embodiment, an ability to access GPUmemories 1320 without cache coherence overheads can be critical toexecution time of an offloaded computation. In at least one embodiment,in cases with substantial streaming write memory traffic, for example,cache coherence overhead can significantly reduce an effective writebandwidth seen by a GPU 1310. In at least one embodiment, efficiency ofoperand setup, efficiency of results access, and efficiency of GPUcomputation may play a role in determining effectiveness of a GPUoffload.

In at least one embodiment, selection of GPU bias and host processorbias is driven by a bias tracker data structure. In at least oneembodiment, a bias table may be used, for example, which may be apage-granular structure (e.g., controlled at a granularity of a memorypage) that includes 1 or 2 bits per GPU-attached memory page. In atleast one embodiment, a bias table may be implemented in a stolen memoryrange of one or more GPU memories 1320, with or without a bias cache ina GPU 1310 (e.g., to cache frequently/recently used entries of a biastable). Alternatively, in at least one embodiment, an entire bias tablemay be maintained within a GPU.

In at least one embodiment, a bias table entry associated with eachaccess to a GPU attached memory 1320 is accessed prior to actual accessto a GPU memory, causing following operations. In at least oneembodiment, local requests from a GPU 1310 that find their page in GPUbias are forwarded directly to a corresponding GPU memory 1320. In atleast one embodiment, local requests from a GPU that find their page inhost bias are forwarded to processor 1305 (e.g., over a high-speed linkas described herein). In at least one embodiment, requests fromprocessor 1305 that find a requested page in host processor biascomplete a request like a normal memory read. Alternatively, requestsdirected to a GPU-biased page may be forwarded to a GPU 1310. In atleast one embodiment, a GPU may then transition a page to a hostprocessor bias if it is not currently using a page. In at least oneembodiment, a bias state of a page can be changed either by asoftware-based mechanism, a hardware-assisted software-based mechanism,or, for a limited set of cases, a purely hardware-based mechanism.

In at least one embodiment, one mechanism for changing bias stateemploys an API call (e.g., OpenCL), which, in turn, calls a GPU's devicedriver which, in turn, sends a message (or enqueues a commanddescriptor) to a GPU directing it to change a bias state and, for sometransitions, perform a cache flushing operation in a host. In at leastone embodiment, a cache flushing operation is used for a transition fromhost processor 1305 bias to GPU bias, but is not for an oppositetransition.

In at least one embodiment, cache coherency is maintained by temporarilyrendering GPU-biased pages uncacheable by host processor 1305. In atleast one embodiment, to access these pages, processor 1305 may requestaccess from GPU 1310, which may or may not grant access right away. Inat least one embodiment, thus, to reduce communication between processor1305 and GPU 1310 it is beneficial to ensure that GPU-biased pages arethose which are required by a GPU but not host processor 1305 and viceversa.

Hardware structure(s) 615 are used to perform one or more embodiments.Details regarding a hardware structure(s) 615 may be provided herein inconjunction with FIGS. 6A and/or 6B.

FIG. 14 illustrates exemplary integrated circuits and associatedgraphics processors that may be fabricated using one or more IP cores,according to various embodiments described herein. In addition to whatis illustrated, other logic and circuits may be included in at least oneembodiment, including additional graphics processors/cores, peripheralinterface controllers, or general-purpose processor cores.

FIG. 14 is a block diagram illustrating an exemplary system on a chipintegrated circuit 1400 that may be fabricated using one or more IPcores, according to at least one embodiment. In at least one embodiment,integrated circuit 1400 includes one or more application processor(s)1405 (e.g., CPUs), at least one graphics processor 1410, and mayadditionally include an image processor 1415 and/or a video processor1420, any of which may be a modular IP core. In at least one embodiment,integrated circuit 1400 includes peripheral or bus logic including a USBcontroller 1425, a UART controller 1430, an SPI/SDIO controller 1435,and an I²2S/I²2C controller 1440. In at least one embodiment, integratedcircuit 1400 can include a display device 1445 coupled to one or more ofa high-definition multimedia interface (HDMI) controller 1450 and amobile industry processor interface (MIPI) display interface 1455. In atleast one embodiment, storage may be provided by a flash memorysubsystem 1460 including flash memory and a flash memory controller. Inat least one embodiment, a memory interface may be provided via a memorycontroller 1465 for access to SDRAM or SRAM memory devices. In at leastone embodiment, some integrated circuits additionally include anembedded security engine 1470.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used inintegrated circuit 1400 for inferencing or predicting operations based,at least in part, on weight parameters calculated using neural networktraining operations, neural network functions and/or architectures, orneural network use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 14 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIGS. 15A-15B illustrate exemplary integrated circuits and associatedgraphics processors that may be fabricated using one or more IP cores,according to various embodiments described herein. In addition to whatis illustrated, other logic and circuits may be included in at least oneembodiment, including additional graphics processors/cores, peripheralinterface controllers, or general-purpose processor cores.

FIGS. 15A-15B are block diagrams illustrating exemplary graphicsprocessors for use within an SoC, according to embodiments describedherein. FIG. 15A illustrates an exemplary graphics processor 1510 of asystem on a chip integrated circuit that may be fabricated using one ormore IP cores, according to at least one embodiment. FIG. 15Billustrates an additional exemplary graphics processor 1540 of a systemon a chip integrated circuit that may be fabricated using one or more IPcores, according to at least one embodiment. In at least one embodiment,graphics processor 1510 of FIG. 15A is a low power graphics processorcore. In at least one embodiment, graphics processor 1540 of FIG. 15B isa higher performance graphics processor core. In at least oneembodiment, each of graphics processors 1510, 1540 can be variants ofgraphics processor 1410 of FIG. 14 .

In at least one embodiment, graphics processor 1510 includes a vertexprocessor 1505 and one or more fragment processor(s) 1515A-1515N (e.g.,1515A, 1515B, 1515C, 1515D, through 1515N-1, and 1515N). In at least oneembodiment, graphics processor 1510 can execute different shaderprograms via separate logic, such that vertex processor 1505 isoptimized to execute operations for vertex shader programs, while one ormore fragment processor(s) 1515A-1515N execute fragment (e.g., pixel)shading operations for fragment or pixel shader programs. In at leastone embodiment, vertex processor 1505 performs a vertex processing stageof a 3D graphics pipeline and generates primitives and vertex data. Inat least one embodiment, fragment processor(s) 1515A-1515N use primitiveand vertex data generated by vertex processor 1505 to produce aframebuffer that is displayed on a display device. In at least oneembodiment, fragment processor(s) 1515A-1515N are optimized to executefragment shader programs as provided for in an OpenGL API, which may beused to perform similar operations as a pixel shader program as providedfor in a Direct 3D API.

In at least one embodiment, graphics processor 1510 additionallyincludes one or more memory management units (MMUs) 1520A-1520B,cache(s) 1525A-1525B, and circuit interconnect(s) 1530A-1530B. In atleast one embodiment, one or more MMU(s) 1520A-1520B provide for virtualto physical address mapping for graphics processor 1510, including forvertex processor 1505 and/or fragment processor(s) 1515A-1515N, whichmay reference vertex or image/texture data stored in memory, in additionto vertex or image/texture data stored in one or more cache(s)1525A-1525B. In at least one embodiment, one or more MMU(s) 1520A-1520Bmay be synchronized with other MMUs within a system, including one ormore MMUs associated with one or more application processor(s) 1405,image processors 1415, and/or video processors 1420 of FIG. 14 , suchthat each processor 1405-1420 can participate in a shared or unifiedvirtual memory system. In at least one embodiment, one or more circuitinterconnect(s) 1530A-1530B enable graphics processor 1510 to interfacewith other IP cores within SoC, either via an internal bus of SoC or viaa direct connection.

In at least one embodiment, graphics processor 1540 includes one or moreshader core(s) 1555A-1555N (e.g., 1555A, 1555B, 1555C, 1555D, 1555E,1555F, through 1555N-1, and 1555N) as shown in FIG. 15B, which providesfor a unified shader core architecture in which a single core or type orcore can execute all types of programmable shader code, including shaderprogram code to implement vertex shaders, fragment shaders, and/orcompute shaders. In at least one embodiment, a number of shader corescan vary. In at least one embodiment, graphics processor 1540 includesan inter-core task manager 1545, which acts as a thread dispatcher todispatch execution threads to one or more shader cores 1555A-1555N and atiling unit 1558 to accelerate tiling operations for tile-basedrendering, in which rendering operations for a scene are subdivided inimage space, for example to exploit local spatial coherence within ascene or to optimize use of internal caches.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIGS. 15A, 15B and may be configured to receive sensor inputs frommultiple sensors and may be trained to infer a coolant requirement. Inat least one embodiment, an inference and/or training logic 615 may beable to infer this using information from historical coolingrequirements and of historical sensor inputs. In at least oneembodiment, an inference and/or training logic 615 may make an inferenceof a change in a cooling requirement. In at least one embodiment, sensorinputs may be correlated to classes of different cooling requirements ofeach of different sensor inputs. In at least one embodiment, a newsensor input classifying within a class of such different sensor inputsmay indicate a cooling requirement, or a change thereof.

FIGS. 16A-16B illustrate additional exemplary graphics processor logicaccording to embodiments described herein. FIG. 16A illustrates agraphics core 1600 that may be included within graphics processor 1410of FIG. 14 , in at least one embodiment, and may be a unified shadercore 1555A-1555N as in FIG. 15B in at least one embodiment. FIG. 16Billustrates a highly-parallel general-purpose graphics processing unit(“GPGPU”) 1630 suitable for deployment on a multi-chip module in atleast one embodiment.

In at least one embodiment, graphics core 1600 includes a sharedinstruction cache 1602, a texture unit 1618, and a cache/shared memory1620 (e.g., including L1, L2, L3, last level cache, or other caches)that are common to execution resources within graphics core 1600. In atleast one embodiment, graphics core 1600 can include multiple slices1601A-1601N or a partition for each core, and a graphics processor caninclude multiple instances of graphics core 1600. In at least oneembodiment, each slice 1601A-1601N refers to graphics core 1600. In atleast one embodiment, slices 1601A-1601N have sub-slices, which are partof a slice 1601A-1601N. In at least one embodiment, slices 1601A-1601Nare independent of other slices or dependent on other slices. In atleast one embodiment, slices 1601A-1601N can include support logicincluding a local instruction cache 1604A-1604N, a thread scheduler(sequencer) 1606A-1606N, a thread dispatcher 1608A-1608N, and a set ofregisters 1610A-1610N. In at least one embodiment, slices 1601A-1601Ncan include a set of additional function units (AFUs 1612A-1612N),floating-point units (FPUs 1614A-1614N), integer arithmetic logic units(ALUs 1616A-1616N), address computational units (ACUs 1613A-1613N),double-precision floating-point units (DPFPUs 1615A-1615N), and matrixprocessing units (MPUs 1617A-1617N).

In at least one embodiment, each slice 1601A-1601N includes one or moreengines for floating point and integer vector operations and one or moreengines to accelerate convolution and matrix operations in AI, machinelearning, or large dataset workloads. In at least one embodiment, one ormore slices 1601A-1601N include one or more vector engines to compute avector (e.g., compute mathematical operations for vectors). In at leastone embodiment, a vector engine can compute a vector operation in 16-bitfloating point (also referred to as “FP16”), 32-bit floating point (alsoreferred to as “FP32”), or 64-bit floating point (also referred to as“FP64”). In at least one embodiment, one or more slices 1601A-1601Nincludes 16 vector engines that are paired with 16 matrix math units tocompute matrix/tensor operations, where vector engines and math unitsare exposed via matrix extensions. In at least one embodiment, a slice aspecified portion of processing resources of a processing unit, e.g., 16cores and a ray tracing unit or 8 cores, a thread scheduler, a threaddispatcher, and additional functional units for a processor. In at leastone embodiment, graphics core 1600 includes one or more matrix enginesto compute matrix operations, e.g., when computing tensor operations.

In at least one embodiment, one or more slices 1601A-1601N includes oneor more ray tracing units to compute ray tracing operations (e.g., 16ray tracing units per slice slices 1601A-1601N). In at least oneembodiment, a ray tracing unit computes ray traversal, triangleintersection, bounding box intersect, or other ray tracing operations.

In at least one embodiment, one or more slices 1601A-1601N includes amedia slice that encodes, decodes, and/or transcodes data; scales and/orformat converts data; and/or performs video quality operations on videodata.

In at least one embodiment, one or more slices 1601A-1601N are linked toL2 cache and memory fabric, link connectors, high-bandwidth memory (HBM)(e.g., HBM2e, HDM3) stacks, and a media engine. In at least oneembodiment, one or more slices 1601A-1601N include multiple cores (e.g.,16 cores) and multiple ray tracing units (e.g., 16) paired to each core.In at least one embodiment, one or more slices 1601A-1601N has one ormore L1 caches. In at least one embodiment, one or more slices1601A-1601N include one or more vector engines; one or more instructioncaches to store instructions; one or more L1 caches to cache data; oneor more shared local memories (SLMs) to store data, e.g., correspondingto instructions; one or more samplers to sample data; one or more raytracing units to perform ray tracing operations; one or more geometriesto perform operations in geometry pipelines and/or apply geometrictransformations to vertices or polygons; one or more rasterizers todescribe an image in vector graphics format (e.g., shape) and convert itinto a raster image (e.g., a series of pixels, dots, or lines, whichwhen displayed together, create an image that is represented by shapes);one or more a Hierarchical Depth Buffer (Hiz) to buffer data; and/or oneor more pixel backends. In at least one embodiment, a slice 1601A-1601Nincludes a memory fabric, e.g., an L2 cache.

In at least one embodiment, FPUs 1614A-1614N can performsingle-precision (32-bit) and half-precision (16-bit) floating pointoperations, while DPFPUs 1615A-1615N perform double precision (64-bit)floating point operations. In at least one embodiment, ALUs 1616A-1616Ncan perform variable precision integer operations at 8-bit, 16-bit, and32-bit precision, and can be configured for mixed precision operations.In at least one embodiment, MPUs 1617A-1617N can also be configured formixed precision matrix operations, including half-precision floatingpoint and 8-bit integer operations. In at least one embodiment, MPUs1617-1617N can perform a variety of matrix operations to acceleratemachine learning application frameworks, including enabling support foraccelerated general matrix to matrix multiplication (GEMM). In at leastone embodiment, AFUs 1612A-1612N can perform additional logic operationsnot supported by floating-point or integer units, includingtrigonometric operations (e.g., sine, cosiInference and/or traininglogic 615 are used to perform inferencing and/or training operationsassociated with one or more embodiments. Details regarding inferenceand/or training logic 615 are provided herein in conjunction with FIGS.6A and/or 6B. In at least one embodiment, inference and/or traininglogic 615 may be used in graphics core 1600 for inferencing orpredicting operations based, at least in part, on weight parameterscalculated using neural network training operations, neural networkfunctions and/or architectures, or neural network use cases describedherein.

In at least one embodiment, graphics core 1600 includes an interconnectand a link fabric sublayer that is attached to a switch and a GPU-GPUbridge that enables multiple graphics processors 1600 (e.g., 8) to beinterlinked without glue to each other with load/store units (LSUs),data transfer units, and sync semantics across multiple graphicsprocessors 1600. In at least one embodiment, interconnects includestandardized interconnects (e.g., PCIe) or some combination thereof.

In at least one embodiment, graphics core 1600 includes multiple tiles.In at least one embodiment, a tile is an individual die or one or moredies, where individual dies can be connected with an interconnect (e.g.,embedded multi-die interconnect bridge (EMIB)). In at least oneembodiment, graphics core 1600 includes a compute tile, a memory tile(e.g., where a memory tile can be exclusively accessed by differenttiles or different chipsets such as a Rambo tile), substrate tile, abase tile, a HMB tile, a link tile, and EMIB tile, where all tiles arepackaged together in graphics core 1600 as part of a GPU. In at leastone embodiment, graphics core 1600 can include multiple tiles in asingle package (also referred to as a “multi tile package”). In at leastone embodiment, a compute tile can have 8 graphics cores 1600, an L1cache; and a base tile can have a host interface with PCIe 5.0, HBM2e,MDFI, and EMIB, a link tile with 8 links, 8 ports with an embeddedswitch. In at least one embodiment, tiles are connected withface-to-face (F2F) chip-on-chip bonding through fine-pitched, 36-micron,microbumps (e.g., copper pillars). In at least one embodiment, graphicscore 1600 includes memory fabric, which includes memory, and is tilethat is accessible by multiple tiles. In at least one embodiment,graphics core 1600 stores, accesses, or loads its own hardware contextsin memory, where a hardware context is a set of data loaded fromregisters before a process resumes, and where a hardware context canindicate a state of hardware (e.g., state of a GPU).

In at least one embodiment, graphics core 1600 includesserializer/deserializer (SERDES) circuitry that converts a serial datastream to a parallel data stream, or converts a parallel data stream toa serial data stream.

In at least one embodiment, graphics core 1600 includes a high speedcoherent unified fabric (GPU to GPU), load/store units, bulk datatransfer and sync semantics, and connected GPUs through an embeddedswitch, where a GPU-GPU bridge is controlled by a controller.

In at least one embodiment, graphics core 1600 performs an API, wheresaid API abstracts hardware of graphics core 1600 and access librarieswith instructions to perform math operations (e.g., math kernellibrary), deep neural network operations (e.g., deep neural networklibrary), vector operations, collective communications, thread buildingblocks, video processing, data analytics library, and/or ray tracingoperations.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 16A and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 16B illustrates a general-purpose processing unit (GPGPU) 1630 thatcan be configured to enable highly-parallel compute operations to beperformed by an array of graphics processing units, in at least oneembodiment. In at least one embodiment, GPGPU 1630 can be linkeddirectly to other instances of GPGPU 1630 to create a multi-GPU clusterto improve training speed for deep neural networks. In at least oneembodiment, GPGPU 1630 includes a host interface 1632 to enable aconnection with a host processor. In at least one embodiment, hostinterface 1632 is a PCI Express interface. In at least one embodiment,host interface 1632 can be a vendor-specific communications interface orcommunications fabric. In at least one embodiment, GPGPU 1630 receivescommands from a host processor and uses a global scheduler 1634 (whichmay be referred to as a thread sequencer and/or asynchronous computeengine) to distribute execution threads associated with those commandsto a set of compute clusters 1636A-1636H. In at least one embodiment,compute clusters 1636A-1636H share a cache memory 1638. In at least oneembodiment, cache memory 1638 can serve as a higher-level cache forcache memories within compute clusters 1636A-1636H.

In at least one embodiment, GPGPU 1630 includes memory 1644A-1644Bcoupled with compute clusters 1636A-1636H via a set of memorycontrollers 1642A-1642B (e.g., one or more controllers for HBM2e). In atleast one embodiment, memory 1644A-1644B can include various types ofmemory devices including dynamic random access memory (DRAM) or graphicsrandom access memory, such as synchronous graphics random access memory(SGRAM), including graphics double data rate (GDDR) memory.

In at least one embodiment, compute clusters 1636A-1636H each include aset of graphics cores, such as graphics core 1600 of FIG. 16A, which caninclude multiple types of integer and floating point logic units thatcan perform computational operations at a range of precisions includingsuited for machine learning computations. For example, in at least oneembodiment, at least a subset of floating point units in each of computeclusters 1636A-1636H can be configured to perform 16-bit or 32-bitfloating point operations, while a different subset of floating pointunits can be configured to perform 64-bit floating point operations.

In at least one embodiment, multiple instances of GPGPU 1630 can beconfigured to operate as a compute cluster. In at least one embodiment,communication used by compute clusters 1636A-1636H for synchronizationand data exchange varies across embodiments. In at least one embodiment,multiple instances of GPGPU 1630 communicate over host interface 1632.In at least one embodiment, GPGPU 1630 includes an I/O hub 1639 thatcouples GPGPU 1630 with a GPU link 1640 that enables a direct connectionto other instances of GPGPU 1630. In at least one embodiment, GPU link1640 is coupled to a dedicated GPU-to-GPU bridge that enablescommunication and synchronization between multiple instances of GPGPU1630. In at least one embodiment, GPU link 1640 couples with ahigh-speed interconnect to transmit and receive data to other GPGPUs orparallel processors. In at least one embodiment, multiple instances ofGPGPU 1630 are located in separate data processing systems andcommunicate via a network device that is accessible via host interface1632. In at least one embodiment GPU link 1640 can be configured toenable a connection to a host processor in addition to or as analternative to host interface 1632.

In at least one embodiment, GPGPU 1630 can be configured to train neuralnetworks. In at least one embodiment, GPGPU 1630 can be used within aninferencing platform. In at least one embodiment, in which GPGPU 1630 isused for inferencing, GPGPU 1630 may include fewer compute clusters1636A-1636H relative to when GPGPU 1630 is used for training a neuralnetwork. In at least one embodiment, memory technology associated withmemory 1644A-1644B may differ between inferencing and trainingconfigurations, with higher bandwidth memory technologies devoted totraining configurations. In at least one embodiment, an inferencingconfiguration of GPGPU 1630 can support inferencing specificinstructions. For example, in at least one embodiment, an inferencingconfiguration can provide support for one or more 8-bit integer dotproduct instructions, which may be used during inferencing operationsfor deployed neural networks.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in GPGPU1630 for inferencing or predicting operations based, at least in part,on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 16 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 17 is a block diagram illustrating a computing system 1700according to at least one embodiment. In at least one embodiment,computing system 1700 includes a processing subsystem 1701 having one ormore processor(s) 1702 and a system memory 1704 communicating via aninterconnection path that may include a memory hub 1705. In at least oneembodiment, memory hub 1705 may be a separate component within a chipsetcomponent or may be integrated within one or more processor(s) 1702. Inat least one embodiment, memory hub 1705 couples with an I/O subsystem1711 via a communication link 1706. In at least one embodiment, I/Osubsystem 1711 includes an I/O hub 1707 that can enable computing system1700 to receive input from one or more input device(s) 1708. In at leastone embodiment, I/O hub 1707 can enable a display controller, which maybe included in one or more processor(s) 1702, to provide outputs to oneor more display device(s) 1710A. In at least one embodiment, one or moredisplay device(s) 1710A coupled with I/O hub 1707 can include a local,internal, or embedded display device.

In at least one embodiment, processing subsystem 1701 includes one ormore parallel processor(s) 1712 coupled to memory hub 1705 via a bus orother communication link 1713. In at least one embodiment, communicationlink 1713 may use one of any number of standards based communicationlink technologies or protocols, such as, but not limited to PCI Express,or may be a vendor-specific communications interface or communicationsfabric. In at least one embodiment, one or more parallel processor(s)1712 form a computationally focused parallel or vector processing systemthat can include a large number of processing cores and/or processingclusters, such as a many-integrated core (MIC) processor. In at leastone embodiment, some or all of parallel processor(s) 1712 form agraphics processing subsystem that can output pixels to one of one ormore display device(s) 1710A coupled via I/O Hub 1707. In at least oneembodiment, parallel processor(s) 1712 can also include a displaycontroller and display interface (not shown) to enable a directconnection to one or more display device(s) 1710B. In at least oneembodiment, parallel processor(s) 1712 include one or more cores, suchas graphics cores 1600 discussed herein.

In at least one embodiment, a system storage unit 1714 can connect toI/O hub 1707 to provide a storage mechanism for computing system 1700.In at least one embodiment, an I/O switch 1716 can be used to provide aninterface mechanism to enable connections between I/O hub 1707 and othercomponents, such as a network adapter 1718 and/or a wireless networkadapter 1719 that may be integrated into platform, and various otherdevices that can be added via one or more add-in device(s) 1720. In atleast one embodiment, network adapter 1718 can be an Ethernet adapter oranother wired network adapter. In at least one embodiment, wirelessnetwork adapter 1719 can include one or more of a Wi-Fi, Bluetooth, nearfield communication (NFC), or other network device that includes one ormore wireless radios.

In at least one embodiment, computing system 1700 can include othercomponents not explicitly shown, including USB or other portconnections, optical storage drives, video capture devices, and like,may also be connected to I/O hub 1707. In at least one embodiment,communication paths interconnecting various components in FIG. 17 may beimplemented using any suitable protocols, such as PCI (PeripheralComponent Interconnect) based protocols (e.g., PCI-Express), or otherbus or point-to-point communication interfaces and/or protocol(s), suchas NV-Link high-speed interconnect, or interconnect protocols.

In at least one embodiment, parallel processor(s) 1712 incorporatecircuitry optimized for graphics and video processing, including, forexample, video output circuitry, and constitutes a graphics processingunit (GPU), e.g., parallel processor(s) 1712 includes graphics core1600. In at least one embodiment, parallel processor(s) 1712 incorporatecircuitry optimized for general purpose processing. In at leastembodiment, components of computing system 1700 may be integrated withone or more other system elements on a single integrated circuit. Forexample, in at least one embodiment, parallel processor(s) 1712, memoryhub 1705, processor(s) 1702, and I/O hub 1707 can be integrated into asystem on chip (SoC) integrated circuit. In at least one embodiment,components of computing system 1700 can be integrated into a singlepackage to form a system in package (SIP) configuration. In at least oneembodiment, at least a portion of components of computing system 1700can be integrated into a multi-chip module (MCM), which can beinterconnected with other multi-chip modules into a modular computingsystem.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in systemFIG. 17 for inferencing or predicting operations based, at least inpart, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

Processors

FIG. 18A illustrates a parallel processor 1800 according to at least oneembodiment. In at least one embodiment, various components of parallelprocessor 1800 may be implemented using one or more integrated circuitdevices, such as programmable processors, application specificintegrated circuits (ASICs), or field programmable gate arrays (FPGA).In at least one embodiment, illustrated parallel processor 1800 is avariant of one or more parallel processor(s) 1712 shown in FIG. 17according to an exemplary embodiment. In at least one embodiment, aparallel processor 1800 includes one or more graphics cores 1600.

In at least one embodiment, parallel processor 1800 includes a parallelprocessing unit 1802. In at least one embodiment, parallel processingunit 1802 includes an I/O unit 1804 that enables communication withother devices, including other instances of parallel processing unit1802. In at least one embodiment, I/O unit 1804 may be directlyconnected to other devices. In at least one embodiment, I/O unit 1804connects with other devices via use of a hub or switch interface, suchas a memory hub 1805. In at least one embodiment, connections betweenmemory hub 1805 and I/O unit 1804 form a communication link 1813. In atleast one embodiment, I/O unit 1804 connects with a host interface 1806and a memory crossbar 1816, where host interface 1806 receives commandsdirected to performing processing operations and memory crossbar 1816receives commands directed to performing memory operations.

In at least one embodiment, when host interface 1806 receives a commandbuffer via I/O unit 1804, host interface 1806 can direct work operationsto perform those commands to a front end 1808. In at least oneembodiment, front end 1808 couples with a scheduler 1810 (which may bereferred to as a sequencer), which is configured to distribute commandsor other work items to a processing cluster array 1812. In at least oneembodiment, scheduler 1810 ensures that processing cluster array 1812 isproperly configured and in a valid state before tasks are distributed toa cluster of processing cluster array 1812. In at least one embodiment,scheduler 1810 is implemented via firmware logic executing on amicrocontroller. In at least one embodiment, microcontroller implementedscheduler 1810 is configurable to perform complex scheduling and workdistribution operations at coarse and fine granularity, enabling rapidpreemption and context switching of threads executing on processingarray 1812. In at least one embodiment, host software can proveworkloads for scheduling on processing cluster array 1812 via one ofmultiple graphics processing paths. In at least one embodiment,workloads can then be automatically distributed across processing arraycluster 1812 by scheduler 1810 logic within a microcontroller includingscheduler 1810.

In at least one embodiment, processing cluster array 1812 can include upto “N” processing clusters (e.g., cluster 1814A, cluster 1814B, throughcluster 1814N), where “N” represents a positive integer (which may be adifferent integer “N” than used in other figures). In at least oneembodiment, each cluster 1814A-1814N of processing cluster array 1812can execute a large number of concurrent threads. In at least oneembodiment, scheduler 1810 can allocate work to clusters 1814A-1814N ofprocessing cluster array 1812 using various scheduling and/or workdistribution algorithms, which may vary depending on workload arisingfor each type of program or computation. In at least one embodiment,scheduling can be handled dynamically by scheduler 1810, or can beassisted in part by compiler logic during compilation of program logicconfigured for execution by processing cluster array 1812. In at leastone embodiment, different clusters 1814A-1814N of processing clusterarray 1812 can be allocated for processing different types of programsor for performing different types of computations.

In at least one embodiment, processing cluster array 1812 can beconfigured to perform various types of parallel processing operations.In at least one embodiment, processing cluster array 1812 is configuredto perform general-purpose parallel compute operations. For example, inat least one embodiment, processing cluster array 1812 can include logicto execute processing tasks including filtering of video and/or audiodata, performing modeling operations, including physics operations, andperforming data transformations.

In at least one embodiment, processing cluster array 1812 is configuredto perform parallel graphics processing operations. In at least oneembodiment, processing cluster array 1812 can include additional logicto support execution of such graphics processing operations, includingbut not limited to, texture sampling logic to perform textureoperations, as well as tessellation logic and other vertex processinglogic. In at least one embodiment, processing cluster array 1812 can beconfigured to execute graphics processing related shader programs suchas, but not limited to, vertex shaders, tessellation shaders, geometryshaders, and pixel shaders. In at least one embodiment, parallelprocessing unit 1802 can transfer data from system memory via I/O unit1804 for processing. In at least one embodiment, during processing,transferred data can be stored to on-chip memory (e.g., parallelprocessor memory 1822) during processing, then written back to systemmemory.

In at least one embodiment, when parallel processing unit 1802 is usedto perform graphics processing, scheduler 1810 can be configured todivide a processing workload into approximately equal sized tasks, tobetter enable distribution of graphics processing operations to multipleclusters 1814A-1814N of processing cluster array 1812. In at least oneembodiment, portions of processing cluster array 1812 can be configuredto perform different types of processing. For example, in at least oneembodiment, a first portion may be configured to perform vertex shadingand topology generation, a second portion may be configured to performtessellation and geometry shading, and a third portion may be configuredto perform pixel shading or other screen space operations, to produce arendered image for display. In at least one embodiment, intermediatedata produced by one or more of clusters 1814A-1814N may be stored inbuffers to allow intermediate data to be transmitted between clusters1814A-1814N for further processing.

In at least one embodiment, processing cluster array 1812 can receiveprocessing tasks to be executed via scheduler 1810, which receivescommands defining processing tasks from front end 1808. In at least oneembodiment, processing tasks can include indices of data to beprocessed, e.g., surface (patch) data, primitive data, vertex data,and/or pixel data, as well as state parameters and commands defining howdata is to be processed (e.g., what program is to be executed). In atleast one embodiment, scheduler 1810 may be configured to fetch indicescorresponding to tasks or may receive indices from front end 1808. In atleast one embodiment, front end 1808 can be configured to ensureprocessing cluster array 1812 is configured to a valid state before aworkload specified by incoming command buffers (e.g., batch-buffers,push buffers, etc.) is initiated.

In at least one embodiment, each of one or more instances of parallelprocessing unit 1802 can couple with a parallel processor memory 1822.In at least one embodiment, parallel processor memory 1822 can beaccessed via memory crossbar 1816, which can receive memory requestsfrom processing cluster array 1812 as well as I/O unit 1804. In at leastone embodiment, memory crossbar 1816 can access parallel processormemory 1822 via a memory interface 1818. In at least one embodiment,memory interface 1818 can include multiple partition units (e.g.,partition unit 1820A, partition unit 1820B, through partition unit1820N) that can each couple to a portion (e.g., memory unit) of parallelprocessor memory 1822. In at least one embodiment, a number of partitionunits 1820A-1820N is configured to be equal to a number of memory units,such that a first partition unit 1820A has a corresponding first memoryunit 1824A, a second partition unit 1820B has a corresponding memoryunit 1824B, and an N-th partition unit 1820N has a corresponding N-thmemory unit 1824N. In at least one embodiment, a number of partitionunits 1820A-1820N may not be equal to a number of memory units.

In at least one embodiment, memory units 1824A-1824N can include varioustypes of memory devices, including dynamic random access memory (DRAM)or graphics random access memory, such as synchronous graphics randomaccess memory (SGRAM), including graphics double data rate (GDDR)memory. In at least one embodiment, memory units 1824A-1824N may alsoinclude 3D stacked memory, including but not limited to high bandwidthmemory (HBM), HBM2e, or HDM3. In at least one embodiment, rendertargets, such as frame buffers or texture maps may be stored acrossmemory units 1824A-1824N, allowing partition units 1820A-1820N to writeportions of each render target in parallel to efficiently use availablebandwidth of parallel processor memory 1822. In at least one embodiment,a local instance of parallel processor memory 1822 may be excluded infavor of a unified memory design that utilizes system memory inconjunction with local cache memory.

In at least one embodiment, any one of clusters 1814A-1814N ofprocessing cluster array 1812 can process data that will be written toany of memory units 1824A-1824N within parallel processor memory 1822.In at least one embodiment, memory crossbar 1816 can be configured totransfer an output of each cluster 1814A-1814N to any partition unit1820A-1820N or to another cluster 1814A-1814N, which can performadditional processing operations on an output. In at least oneembodiment, each cluster 1814A-1814N can communicate with memoryinterface 1818 through memory crossbar 1816 to read from or write tovarious external memory devices. In at least one embodiment, memorycrossbar 1816 has a connection to memory interface 1818 to communicatewith I/O unit 1804, as well as a connection to a local instance ofparallel processor memory 1822, enabling processing units withindifferent processing clusters 1814A-1814N to communicate with systemmemory or other memory that is not local to parallel processing unit1802. In at least one embodiment, memory crossbar 1816 can use virtualchannels to separate traffic streams between clusters 1814A-1814N andpartition units 1820A-1820N.

In at least one embodiment, multiple instances of parallel processingunit 1802 can be provided on a single add-in card, or multiple add-incards can be interconnected. In at least one embodiment, differentinstances of parallel processing unit 1802 can be configured tointeroperate even if different instances have different numbers ofprocessing cores, different amounts of local parallel processor memory,and/or other configuration differences. For example, in at least oneembodiment, some instances of parallel processing unit 1802 can includehigher precision floating point units relative to other instances. In atleast one embodiment, systems incorporating one or more instances ofparallel processing unit 1802 or parallel processor 1800 can beimplemented in a variety of configurations and form factors, includingbut not limited to desktop, laptop, or handheld personal computers,servers, workstations, game consoles, and/or embedded systems.

FIG. 18B is a block diagram of a partition unit 1820 according to atleast one embodiment. In at least one embodiment, partition unit 1820 isan instance of one of partition units 1820A-1820N of FIG. 18A. In atleast one embodiment, partition unit 1820 includes an L2 cache 1821, aframe buffer interface 1825, and a ROP 1826 (raster operations unit). Inat least one embodiment, L2 cache 1821 is a read/write cache that isconfigured to perform load and store operations received from memorycrossbar 1816 and ROP 1826. In at least one embodiment, read misses andurgent write-back requests are output by L2 cache 1821 to frame bufferinterface 1825 for processing. In at least one embodiment, updates canalso be sent to a frame buffer via frame buffer interface 1825 forprocessing. In at least one embodiment, frame buffer interface 1825interfaces with one of memory units in parallel processor memory, suchas memory units 1824A-1824N of FIG. 18 (e.g., within parallel processormemory 1822).

In at least one embodiment, ROP 1826 is a processing unit that performsraster operations such as stencil, z test, blending, etc. In at leastone embodiment, ROP 1826 then outputs processed graphics data that isstored in graphics memory. In at least one embodiment, ROP 1826 includescompression logic to compress depth or color data that is written tomemory and decompress depth or color data that is read from memory. Inat least one embodiment, compression logic can be lossless compressionlogic that makes use of one or more of multiple compression algorithms.In at least one embodiment, a type of compression that is performed byROP 1826 can vary based on statistical characteristics of data to becompressed. For example, in at least one embodiment, delta colorcompression is performed on depth and color data on a per-tile basis.

In at least one embodiment, ROP 1826 is included within each processingcluster (e.g., cluster 1814A-1814N of FIG. 18A) instead of withinpartition unit 1820. In at least one embodiment, read and write requestsfor pixel data are transmitted over memory crossbar 1816 instead ofpixel fragment data. In at least one embodiment, processed graphics datamay be displayed on a display device, such as one of one or more displaydevice(s) 1710 of FIG. 17 , routed for further processing byprocessor(s) 1702, or routed for further processing by one of processingentities within parallel processor 1800 of FIG. 18A.

FIG. 18C is a block diagram of a processing cluster 1814 within aparallel processing unit according to at least one embodiment. In atleast one embodiment, a processing cluster is an instance of one ofprocessing clusters 1814A-1814N of FIG. 18A. In at least one embodiment,processing cluster 1814 can be configured to execute many threads inparallel, where “thread” refers to an instance of a particular programexecuting on a particular set of input data. In at least one embodiment,single-instruction, multiple-data (SIMD) instruction issue techniquesare used to support parallel execution of a large number of threadswithout providing multiple independent instruction units. In at leastone embodiment, single-instruction, multiple-thread (SIMT) techniquesare used to support parallel execution of a large number of generallysynchronized threads, using a common instruction unit configured toissue instructions to a set of processing engines within each one ofprocessing clusters.

In at least one embodiment, operation of processing cluster 1814 can becontrolled via a pipeline manager 1832 that distributes processing tasksto SIMT parallel processors. In at least one embodiment, pipelinemanager 1832 receives instructions from scheduler 1810 of FIG. 18A andmanages execution of those instructions via a graphics multiprocessor1834 and/or a texture unit 1836. In at least one embodiment, graphicsmultiprocessor 1834 is an exemplary instance of a SIMT parallelprocessor. However, in at least one embodiment, various types of SIMTparallel processors of differing architectures may be included withinprocessing cluster 1814. In at least one embodiment, one or moreinstances of graphics multiprocessor 1834 can be included within aprocessing cluster 1814. In at least one embodiment, graphicsmultiprocessor 1834 can process data and a data crossbar 1840 can beused to distribute processed data to one of multiple possibledestinations, including other shader units. In at least one embodiment,pipeline manager 1832 can facilitate distribution of processed data byspecifying destinations for processed data to be distributed via datacrossbar 1840.

In at least one embodiment, each graphics multiprocessor 1834 withinprocessing cluster 1814 can include an identical set of functionalexecution logic (e.g., arithmetic logic units, load-store units, etc.).In at least one embodiment, functional execution logic can be configuredin a pipelined manner in which new instructions can be issued beforeprevious instructions are complete. In at least one embodiment,functional execution logic supports a variety of operations includinginteger and floating point arithmetic, comparison operations, Booleanoperations, bit-shifting, and computation of various algebraicfunctions. In at least one embodiment, same functional-unit hardware canbe leveraged to perform different operations and any combination offunctional units may be present.

In at least one embodiment, instructions transmitted to processingcluster 1814 constitute a thread. In at least one embodiment, a set ofthreads executing across a set of parallel processing engines is athread group. In at least one embodiment, a thread group executes acommon program on different input data. In at least one embodiment, eachthread within a thread group can be assigned to a different processingengine within a graphics multiprocessor 1834. In at least oneembodiment, a thread group may include fewer threads than a number ofprocessing engines within graphics multiprocessor 1834. In at least oneembodiment, when a thread group includes fewer threads than a number ofprocessing engines, one or more of processing engines may be idle duringcycles in which that thread group is being processed. In at least oneembodiment, a thread group may also include more threads than a numberof processing engines within graphics multiprocessor 1834. In at leastone embodiment, when a thread group includes more threads than number ofprocessing engines within graphics multiprocessor 1834, processing canbe performed over consecutive clock cycles. In at least one embodiment,multiple thread groups can be executed concurrently on a graphicsmultiprocessor 1834.

In at least one embodiment, graphics multiprocessor 1834 includes aninternal cache memory to perform load and store operations. In at leastone embodiment, graphics multiprocessor 1834 can forego an internalcache and use a cache memory (e.g., L1 cache 1848) within processingcluster 1814. In at least one embodiment, each graphics multiprocessor1834 also has access to L2 caches within partition units (e.g.,partition units 1820A-1820N of FIG. 18A) that are shared among allprocessing clusters 1814 and may be used to transfer data betweenthreads. In at least one embodiment, graphics multiprocessor 1834 mayalso access off-chip global memory, which can include one or more oflocal parallel processor memory and/or system memory. In at least oneembodiment, any memory external to parallel processing unit 1802 may beused as global memory. In at least one embodiment, processing cluster1814 includes multiple instances of graphics multiprocessor 1834 and canshare common instructions and data, which may be stored in L1 cache1848.

In at least one embodiment, each processing cluster 1814 may include anMMU 1845 (memory management unit) that is configured to map virtualaddresses into physical addresses. In at least one embodiment, one ormore instances of MMU 1845 may reside within memory interface 1818 ofFIG. 18A. In at least one embodiment, MMU 1845 includes a set of pagetable entries (PTEs) used to map a virtual address to a physical addressof a tile and optionally a cache line index. In at least one embodiment,MMU 1845 may include address translation lookaside buffers (TLB) orcaches that may reside within graphics multiprocessor 1834 or L1 1848cache or processing cluster 1814. In at least one embodiment, a physicaladdress is processed to distribute surface data access locally to allowfor efficient request interleaving among partition units. In at leastone embodiment, a cache line index may be used to determine whether arequest for a cache line is a hit or miss.

In at least one embodiment, a processing cluster 1814 may be configuredsuch that each graphics multiprocessor 1834 is coupled to a texture unit1836 for performing texture mapping operations, e.g., determiningtexture sample positions, reading texture data, and filtering texturedata. In at least one embodiment, texture data is read from an internaltexture L1 cache (not shown) or from an L1 cache within graphicsmultiprocessor 1834 and is fetched from an L2 cache, local parallelprocessor memory, or system memory, as needed. In at least oneembodiment, each graphics multiprocessor 1834 outputs processed tasks todata crossbar 1840 to provide processed task to another processingcluster 1814 for further processing or to store processed task in an L2cache, local parallel processor memory, or system memory via memorycrossbar 1816. In at least one embodiment, a preROP 1842 (pre-rasteroperations unit) is configured to receive data from graphicsmultiprocessor 1834, and direct data to ROP units, which may be locatedwith partition units as described herein (e.g., partition units1820A-1820N of FIG. 18A). In at least one embodiment, preROP 1842 unitcan perform optimizations for color blending, organizing pixel colordata, and performing address translations.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in graphicsprocessing cluster 1814 for inferencing or predicting operations based,at least in part, on weight parameters calculated using neural networktraining operations, neural network functions and/or architectures, orneural network use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIGS. 18A-C and may be configured to receive sensor inputs frommultiple sensors and may be trained to infer a coolant requirement. Inat least one embodiment, an inference and/or training logic 615 may beable to infer this using information from historical coolingrequirements and of historical sensor inputs. In at least oneembodiment, an inference and/or training logic 615 may make an inferenceof a change in a cooling requirement. In at least one embodiment, sensorinputs may be correlated to classes of different cooling requirements ofeach of different sensor inputs. In at least one embodiment, a newsensor input classifying within a class of such different sensor inputsmay indicate a cooling requirement, or a change thereof.

FIG. 18D shows a graphics multiprocessor 1834 according to at least oneembodiment. In at least one embodiment, graphics multiprocessor 1834couples with pipeline manager 1832 of processing cluster 1814. In atleast one embodiment, graphics multiprocessor 1834 has an executionpipeline including but not limited to an instruction cache 1852, aninstruction unit 1854, an address mapping unit 1856, a register file1858, one or more general purpose graphics processing unit (GPGPU) cores1862, and one or more load/store units 1866, where one or moreload/store units 1866 can perform load/store operations to load/storeinstructions corresponding to performing an operation. In at least oneembodiment, GPGPU cores 1862 and load/store units 1866 are coupled withcache memory 1872 and shared memory 1870 via a memory and cacheinterconnect 1868.

In at least one embodiment, instruction cache 1852 receives a stream ofinstructions to execute from pipeline manager 1832. In at least oneembodiment, instructions are cached in instruction cache 1852 anddispatched for execution by an instruction unit 1854. In at least oneembodiment, instruction unit 1854 can dispatch instructions as threadgroups (e.g., warps, wavefronts, waves), with each thread of threadgroup assigned to a different execution unit within GPGPU cores 1862. Inat least one embodiment, an instruction can access any of a local,shared, or global address space by specifying an address within aunified address space. In at least one embodiment, address mapping unit1856 can be used to translate addresses in a unified address space intoa distinct memory address that can be accessed by load/store units 1866.

In at least one embodiment, register file 1858 provides a set ofregisters for functional units of graphics multiprocessor 1834. In atleast one embodiment, register file 1858 provides temporary storage foroperands connected to data paths of functional units (e.g., GPGPU cores1862, load/store units 1866) of graphics multiprocessor 1834. In atleast one embodiment, register file 1858 is divided between each offunctional units such that each functional unit is allocated a dedicatedportion of register file 1858. In at least one embodiment, register file1858 is divided between different warps (which may be referred to aswavefronts and/or waves) being executed by graphics multiprocessor 1834.

In at least one embodiment, GPGPU cores 1862 can each include floatingpoint units (FPUs) and/or integer arithmetic logic units (ALUs) that areused to execute instructions of graphics multiprocessor 1834. In atleast one embodiment, GPGPU cores 1862 can be similar in architecture orcan differ in architecture. In at least one embodiment, a first portionof GPGPU cores 1862 include a single precision FPU and an integer ALUwhile a second portion of GPGPU cores include a double precision FPU. Inat least one embodiment, FPUs can implement IEEE 754-2008 standardfloating point arithmetic or enable variable precision floating pointarithmetic. In at least one embodiment, graphics multiprocessor 1834 canadditionally include one or more fixed function or special functionunits to perform specific functions such as copy rectangle or pixelblending operations. In at least one embodiment, one or more of GPGPUcores 1862 can also include fixed or special function logic.

In at least one embodiment, GPGPU cores 1862 include SIMD logic capableof performing a single instruction on multiple sets of data. In at leastone embodiment, GPGPU cores 1862 can physically execute SIMD4, SIMD8,and SIMD16 instructions and logically execute SIMD1, SIMD2, and SIMD32instructions. In at least one embodiment, SIMD instructions for GPGPUcores can be generated at compile time by a shader compiler orautomatically generated when executing programs written and compiled forsingle program multiple data (SPMD) or SIMT architectures. In at leastone embodiment, multiple threads of a program configured for an SIMTexecution model can executed via a single SIMD instruction. For example,in at least one embodiment, eight SIMT threads that perform same orsimilar operations can be executed in parallel via a single SIMD8 logicunit.

In at least one embodiment, memory and cache interconnect 1868 is aninterconnect network that connects each functional unit of graphicsmultiprocessor 1834 to register file 1858 and to shared memory 1870. Inat least one embodiment, memory and cache interconnect 1868 is acrossbar interconnect that allows load/store unit 1866 to implement loadand store operations between shared memory 1870 and register file 1858.In at least one embodiment, register file 1858 can operate at a samefrequency as GPGPU cores 1862, thus data transfer between GPGPU cores1862 and register file 1858 can have very low latency. In at least oneembodiment, shared memory 1870 can be used to enable communicationbetween threads that execute on functional units within graphicsmultiprocessor 1834. In at least one embodiment, cache memory 1872 canbe used as a data cache for example, to cache texture data communicatedbetween functional units and texture unit 1836. In at least oneembodiment, shared memory 1870 can also be used as a program managedcache. In at least one embodiment, threads executing on GPGPU cores 1862can programmatically store data within shared memory in addition toautomatically cached data that is stored within cache memory 1872.

In at least one embodiment, a parallel processor or GPGPU as describedherein is communicatively coupled to host/processor cores to accelerategraphics operations, machine-learning operations, pattern analysisoperations, and various general purpose GPU (GPGPU) functions. In atleast one embodiment, a GPU may be communicatively coupled to hostprocessor/cores over a bus or other interconnect (e.g., a high-speedinterconnect such as PCIe or NVLink). In at least one embodiment, a GPUmay be integrated on a package or chip as cores and communicativelycoupled to cores over an internal processor bus/interconnect internal toa package or chip. In at least one embodiment, regardless a manner inwhich a GPU is connected, processor cores may allocate work to such GPUin a form of sequences of commands/instructions contained in a workdescriptor. In at least one embodiment, that GPU then uses dedicatedcircuitry/logic for efficiently processing these commands/instructions.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in graphicsmultiprocessor 1834 for inferencing or predicting operations based, atleast in part, on weight parameters calculated using neural networktraining operations, neural network functions and/or architectures, orneural network use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 18D and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 19 illustrates a multi-GPU computing system 1900, according to atleast one embodiment. In at least one embodiment, multi-GPU computingsystem 1900 can include a processor 1902 coupled to multiple generalpurpose graphics processing units (GPGPUs) 1906A-D via a host interfaceswitch 1904. In at least one embodiment, host interface switch 1904 is aPCI express switch device that couples processor 1902 to a PCI expressbus over which processor 1902 can communicate with GPGPUs 1906A-D. In atleast one embodiment, GPGPUs 1906A-D can interconnect via a set ofhigh-speed point-to-point GPU-to-GPU links 1916. In at least oneembodiment, GPU-to-GPU links 1916 connect to each of GPGPUs 1906A-D viaa dedicated GPU link. In at least one embodiment, P2P GPU links 1916enable direct communication between each of GPGPUs 1906A-D withoutrequiring communication over host interface bus 1904 to which processor1902 is connected. In at least one embodiment, with GPU-to-GPU trafficdirected to P2P GPU links 1916, host interface bus 1904 remainsavailable for system memory access or to communicate with otherinstances of multi-GPU computing system 1900, for example, via one ormore network devices. While in at least one embodiment GPGPUs 1906A-Dconnect to processor 1902 via host interface switch 1904, in at leastone embodiment processor 1902 includes direct support for P2P GPU links1916 and can connect directly to GPGPUs 1906A-D.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in multi-GPUcomputing system 1900 for inferencing or predicting operations based, atleast in part, on weight parameters calculated using neural networktraining operations, neural network functions and/or architectures, orneural network use cases described herein.

In at least one embodiment, multi-GPU computing system 1900 includes oneor more graphics cores 1600.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 19 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 20 is a block diagram of a graphics processor 2000, according to atleast one embodiment. In at least one embodiment, graphics processor2000 includes a ring interconnect 2002, a pipeline front-end 2004, amedia engine 2037, and graphics cores 2080A-2080N. In at least oneembodiment, ring interconnect 2002 couples graphics processor 2000 toother processing units, including other graphics processors or one ormore general-purpose processor cores. In at least one embodiment,graphics processor 2000 is one of many processors integrated within amulti-core processing system. In at least one embodiment, graphicsprocessor 2000 includes graphics core 1600.

In at least one embodiment, graphics processor 2000 receives batches ofcommands via ring interconnect 2002. In at least one embodiment,incoming commands are interpreted by a command streamer 2003 in pipelinefront-end 2004. In at least one embodiment, graphics processor 2000includes scalable execution logic to perform 3D geometry processing andmedia processing via graphics core(s) 2080A-2080N. In at least oneembodiment, for 3D geometry processing commands, command streamer 2003supplies commands to geometry pipeline 2036. In at least one embodiment,for at least some media processing commands, command streamer 2003supplies commands to a video front end 2034, which couples with mediaengine 2037. In at least one embodiment, media engine 2037 includes aVideo Quality Engine (VQE) 2030 for video and image post-processing anda multi-format encode/decode (MFX) 2033 engine to providehardware-accelerated media data encoding and decoding. In at least oneembodiment, geometry pipeline 2036 and media engine 2037 each generateexecution threads for thread execution resources provided by at leastone graphics core 2080.

In at least one embodiment, graphics processor 2000 includes scalablethread execution resources featuring graphics cores 2080A-2080N (whichcan be modular and are sometimes referred to as core slices), eachhaving multiple sub-cores 2050A-50N, 2060A-2060N (sometimes referred toas core sub-slices). In at least one embodiment, graphics processor 2000can have any number of graphics cores 2080A. In at least one embodiment,graphics processor 2000 includes a graphics core 2080A having at least afirst sub-core 2050A and a second sub-core 2060A. In at least oneembodiment, graphics processor 2000 is a low power processor with asingle sub-core (e.g., 2050A). In at least one embodiment, graphicsprocessor 2000 includes multiple graphics cores 2080A-2080N, eachincluding a set of first sub-cores 2050A-2050N and a set of secondsub-cores 2060A-2060N. In at least one embodiment, each sub-core infirst sub-cores 2050A-2050N includes at least a first set of executionunits 2052A-2052N and media/texture samplers 2054A-2054N. In at leastone embodiment, each sub-core in second sub-cores 2060A-2060N includesat least a second set of execution units 2062A-2062N and samplers2064A-2064N. In at least one embodiment, each sub-core 2050A-2050N,2060A-2060N shares a set of shared resources 2070A-2070N. In at leastone embodiment, shared resources include shared cache memory and pixeloperation logic. In at least one embodiment, graphics processor 2000includes load/store units in pipeline front-end 2004.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, inference and/or training logic 615 may be used in graphicsprocessor 2000 for inferencing or predicting operations based, at leastin part, on weight parameters calculated using neural network trainingoperations, neural network functions and/or architectures, or neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 20 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 21 is a block diagram illustrating micro-architecture for aprocessor 2100 that may include logic circuits to perform instructions,according to at least one embodiment. In at least one embodiment,processor 2100 may perform instructions, including x86 instructions, ARMinstructions, specialized instructions for application-specificintegrated circuits (ASICs), etc. In at least one embodiment, processor2100 may include registers to store packed data, such as 64-bit wideMMX™ registers in microprocessors enabled with MMX technology from IntelCorporation of Santa Clara, Calif. In at least one embodiment, MMXregisters, available in both integer and floating point forms, mayoperate with packed data elements that accompany single instruction,multiple data (“SIMD”) and streaming SIMD extensions (“SSE”)instructions. In at least one embodiment, 128-bit wide XMM registersrelating to SSE2, SSE3, SSE4, AVX, or beyond (referred to generically as“SSEx”) technology may hold such packed data operands. In at least oneembodiment, processor 2100 may perform instructions to acceleratemachine learning or deep learning algorithms, training, or inferencing.

In at least one embodiment, processor 2100 includes an in-order frontend (“front end”) 2101 to fetch instructions to be executed and prepareinstructions to be used later in a processor pipeline. In at least oneembodiment, front end 2101 may include several units. In at least oneembodiment, an instruction prefetcher 2126 fetches instructions frommemory and feeds instructions to an instruction decoder 2128 which inturn decodes or interprets instructions. For example, in at least oneembodiment, instruction decoder 2128 decodes a received instruction intoone or more operations called “micro-instructions” or “micro-operations”(also called “micro ops” or “uops” or “μ-ops”) that a machine mayexecute. In at least one embodiment, instruction decoder 2128 parses aninstruction into an opcode and corresponding data and control fieldsthat may be used by micro-architecture to perform operations inaccordance with at least one embodiment. In at least one embodiment, atrace cache 2130 may assemble decoded uops into program orderedsequences or traces in a uop queue 2134 for execution. In at least oneembodiment, when trace cache 2130 encounters a complex instruction, amicrocode ROM 2132 provides uops needed to complete an operation.

In at least one embodiment, some instructions may be converted into asingle micro-op, whereas others need several micro-ops to complete fulloperation. In at least one embodiment, if more than four micro-ops areneeded to complete an instruction, instruction decoder 2128 may accessmicrocode ROM 2132 to perform that instruction. In at least oneembodiment, an instruction may be decoded into a small number ofmicro-ops for processing at instruction decoder 2128. In at least oneembodiment, an instruction may be stored within microcode ROM 2132should a number of micro-ops be needed to accomplish such operation. Inat least one embodiment, trace cache 2130 refers to an entry pointprogrammable logic array (“PLA”) to determine a correctmicro-instruction pointer for reading microcode sequences to completeone or more instructions from microcode ROM 2132 in accordance with atleast one embodiment. In at least one embodiment, after microcode ROM2132 finishes sequencing micro-ops for an instruction, front end 2101 ofa machine may resume fetching micro-ops from trace cache 2130.

In at least one embodiment, out-of-order execution engine (“out of orderengine”) 2103 may prepare instructions for execution. In at least oneembodiment, out-of-order execution logic has a number of buffers tosmooth out and re-order flow of instructions to optimize performance asthey go down a pipeline and get scheduled for execution. In at least oneembodiment, out-of-order execution engine 2103 includes, withoutlimitation, an allocator/register renamer 2140, a memory uop queue 2142,an integer/floating point uop queue 2144, a memory scheduler 2146, afast scheduler 2102, a slow/general floating point scheduler(“slow/general FP scheduler”) 2104, and a simple floating pointscheduler (“simple FP scheduler”) 2106. In at least one embodiment, fastschedule 2102, slow/general floating point scheduler 2104, and simplefloating point scheduler 2106 are also collectively referred to hereinas “uop schedulers 2102, 2104, 2106.” In at least one embodiment,allocator/register renamer 2140 allocates machine buffers and resourcesthat each uop needs in order to execute. In at least one embodiment,allocator/register renamer 2140 renames logic registers onto entries ina register file. In at least one embodiment, allocator/register renamer2140 also allocates an entry for each uop in one of two uop queues,memory uop queue 2142 for memory operations and integer/floating pointuop queue 2144 for non-memory operations, in front of memory scheduler2146 and uop schedulers 2102, 2104, 2106. In at least one embodiment,uop schedulers 2102, 2104, 2106, determine when a uop is ready toexecute based on readiness of their dependent input register operandsources and availability of execution resources uops need to completetheir operation. In at least one embodiment, fast scheduler 2102 mayschedule on each half of a main clock cycle while slow/general floatingpoint scheduler 2104 and simple floating point scheduler 2106 mayschedule once per main processor clock cycle. In at least oneembodiment, uop schedulers 2102, 2104, 2106 arbitrate for dispatch portsto schedule uops for execution.

In at least one embodiment, execution block 2111 includes, withoutlimitation, an integer register file/bypass network 2108, a floatingpoint register file/bypass network (“FP register file/bypass network”)2110, address generation units (“AGUs”) 2112 and 2114, fast ArithmeticLogic Units (ALUs) (“fast ALUs”) 2116 and 2118, a slow Arithmetic LogicUnit (“slow ALU”) 2120, a floating point ALU (“FP”) 2122, and a floatingpoint move unit (“FP move”) 2124. In at least one embodiment, integerregister file/bypass network 2108 and floating point registerfile/bypass network 2110 are also referred to herein as “register files2108, 2110.” In at least one embodiment, AGUSs 2112 and 2114, fast ALUs2116 and 2118, slow ALU 2120, floating point ALU 2122, and floatingpoint move unit 2124 are also referred to herein as “execution units2112, 2114, 2116, 2118, 2120, 2122, and 2124.” In at least oneembodiment, execution block 2111 may include, without limitation, anynumber (including zero) and type of register files, bypass networks,address generation units, and execution units, in any combination.

In at least one embodiment, register networks 2108, 2110 may be arrangedbetween uop schedulers 2102, 2104, 2106, and execution units 2112, 2114,2116, 2118, 2120, 2122, and 2124. In at least one embodiment, integerregister file/bypass network 2108 performs integer operations. In atleast one embodiment, floating point register file/bypass network 2110performs floating point operations. In at least one embodiment, each ofregister networks 2108, 2110 may include, without limitation, a bypassnetwork that may bypass or forward just completed results that have notyet been written into a register file to new dependent uops. In at leastone embodiment, register networks 2108, 2110 may communicate data witheach other. In at least one embodiment, integer register file/bypassnetwork 2108 may include, without limitation, two separate registerfiles, one register file for a low-order thirty-two bits of data and asecond register file for a high order thirty-two bits of data. In atleast one embodiment, floating point register file/bypass network 2110may include, without limitation, 128-bit wide entries because floatingpoint instructions typically have operands from 64 to 128 bits in width.

In at least one embodiment, execution units 2112, 2114, 2116, 2118,2120, 2122, 2124 may execute instructions. In at least one embodiment,register networks 2108, 2110 store integer and floating point dataoperand values that micro-instructions need to execute. In at least oneembodiment, processor 2100 may include, without limitation, any numberand combination of execution units 2112, 2114, 2116, 2118, 2120, 2122,2124. In at least one embodiment, floating point ALU 2122 and floatingpoint move unit 2124, may execute floating point, MMX, SIMD, AVX andSSE, or other operations, including specialized machine learninginstructions. In at least one embodiment, floating point ALU 2122 mayinclude, without limitation, a 64-bit by 64-bit floating point dividerto execute divide, square root, and remainder micro ops. In at least oneembodiment, instructions involving a floating point value may be handledwith floating point hardware. In at least one embodiment, ALU operationsmay be passed to fast ALUs 2116, 2118. In at least one embodiment, fastALUS 2116, 2118 may execute fast operations with an effective latency ofhalf a clock cycle. In at least one embodiment, most complex integeroperations go to slow ALU 2120 as slow ALU 2120 may include, withoutlimitation, integer execution hardware for long-latency type ofoperations, such as a multiplier, shifts, flag logic, and branchprocessing. In at least one embodiment, memory load/store operations maybe executed by AGUs 2112, 2114. In at least one embodiment, fast ALU2116, fast ALU 2118, and slow ALU 2120 may perform integer operations on64-bit data operands. In at least one embodiment, fast ALU 2116, fastALU 2118, and slow ALU 2120 may be implemented to support a variety ofdata bit sizes including sixteen, thirty-two, 128, 256, etc. In at leastone embodiment, floating point ALU 2122 and floating point move unit2124 may be implemented to support a range of operands having bits ofvarious widths, such as 128-bit wide packed data operands in conjunctionwith SIMD and multimedia instructions.

In at least one embodiment, uop schedulers 2102, 2104, 2106 dispatchdependent operations before a parent load has finished executing. In atleast one embodiment, as uops may be speculatively scheduled andexecuted in processor 2100, processor 2100 may also include logic tohandle memory misses. In at least one embodiment, if a data load missesin a data cache, there may be dependent operations in flight in apipeline that have left a scheduler with temporarily incorrect data. Inat least one embodiment, a replay mechanism tracks and re-executesinstructions that use incorrect data. In at least one embodiment,dependent operations might need to be replayed and independent ones maybe allowed to complete. In at least one embodiment, schedulers and areplay mechanism of at least one embodiment of a processor may also bedesigned to catch instruction sequences for text string comparisonoperations.

In at least one embodiment, “registers” may refer to on-board processorstorage locations that may be used as part of instructions to identifyoperands. In at least one embodiment, registers may be those that may beusable from outside of a processor (from a programmer's perspective). Inat least one embodiment, registers might not be limited to a particulartype of circuit. Rather, in at least one embodiment, a register maystore data, provide data, and perform functions described herein. In atleast one embodiment, registers described herein may be implemented bycircuitry within a processor using any number of different techniques,such as dedicated physical registers, dynamically allocated physicalregisters using register renaming, combinations of dedicated anddynamically allocated physical registers, etc. In at least oneembodiment, integer registers store 32-bit integer data. A register fileof at least one embodiment also contains eight multimedia SIMD registersfor packed data.

In at least one embodiment, processor 2100 or each core of processor2100 includes one or more prefetchers, one or more fetchers, one or morepre-decoders, one or more decoders to decode data (e.g., instructions),one or more instruction queues to process instructions (e.g.,corresponding to operations or API calls), one or more micro-operation(μOP) cache to store μOPs, one or more micro-operation (μOP) queues, anin-order execution engine, one or more load buffers, one or more storebuffers, one or more reorder buffers, one or more fill buffers, anout-of-order execution engine, one or more ports, one or more shiftand/or shifter units, one or more fused multiply accumulate (FMA) units,one or more load and store units (“LSUs”) to perform load of storeoperations corresponding to loading/storing data (e.g., instructions) toperform an operation (e.g., perform an API, an API call), one or morematrix multiply accumulate (MMA) units, and/or one or more shuffle unitsto perform any function further described herein with respect to saidprocessor 2100. In at least one embodiment processor 2100 can access,use, perform, or execute instructions corresponding to calling an API.

In at least one embodiment, processor 2100 includes one or more ultrapath interconnects (UPIs), e.g., that is a point-to-point processorinterconnect; one or more PCIe's; one or more accelerators to acceleratecomputations or operations; and/or one or more memory controllers. In atleast one embodiment, processor 2100 includes a shared last level cache(LLC) that is coupled to one or more memory controllers, which canenable shared memory access across processor cores.

In at least one embodiment, processor 2100 or a core of processor 2100has a mesh architecture where processor cores, on-chip caches, memorycontrollers, and I/O controllers are organized in rows and columns, withwires and switches connecting them at each intersection to allow forturns. In at least one embodiment, processor 2100 has a one or morehigher memory bandwidths (HMBs, e.g., HMBe) to store data or cache data,e.g., in Double Data Rate 5 Synchronous Dynamic Random-Access Memory(DDR5 SDRAM). In at least one embodiment, one or more components ofprocessor 2100 are interconnected using compute express link (CXL)interconnects. In at least one embodiment, a memory controller uses a“least recently used” (LRU) approach to determine what gets stored in acache. In at least one embodiment, processor 2100 includes one or morePCIe's (e.g., PCIe 5.0).

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment portions or all of inference and/or training logic 615 may beincorporated into execution block 2111 and other memory or registersshown or not shown. For example, in at least one embodiment, trainingand/or inferencing techniques described herein may use one or more ofALUs illustrated in execution block 2111. Moreover, weight parametersmay be stored in on-chip or off-chip memory and/or registers (shown ornot shown) that configure ALUs of execution block 2111 to perform one ormore machine learning algorithms, neural network architectures, usecases, or training techniques described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 21 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 22 illustrates a deep learning application processor 2200,according to at least one embodiment. In at least one embodiment, deeplearning application processor 2200 uses instructions that, if executedby deep learning application processor 2200, cause deep learningapplication processor 2200 to perform some or all of processes andtechniques described throughout this disclosure. In at least oneembodiment, deep learning application processor 2200 is anapplication-specific integrated circuit (ASIC). In at least oneembodiment, application processor 2200 performs matrix multiplyoperations either “hard-wired” into hardware as a result of performingone or more instructions or both. In at least one embodiment, deeplearning application processor 2200 includes, without limitation,processing clusters 2210(1)-2210(12), Inter-Chip Links (“ICLs”)2220(1)-2220(12), Inter-Chip Controllers (“ICCs”) 2230(1)-2230(2),high-bandwidth memory second generation (“HBM2”) 2240(1)-2240(4), memorycontrollers (“Mem Ctrlrs”) 2242(1)-2242(4), high bandwidth memoryphysical layer (“HBM PHY”) 2244(1)-2244(4), a management-controllercentral processing unit (“management-controller CPU”) 2250, a SerialPeripheral Interface, Inter-Integrated Circuit, and General PurposeInput/Output block (“SPI, I²C, GPIO”) 2260, a peripheral componentinterconnect express controller and direct memory access block (“PCIeController and DMA”) 2270, and a sixteen-lane peripheral componentinterconnect express port (“PCI Express x 16”) 2280.

In at least one embodiment, processing clusters 2210 may perform deeplearning operations, including inference or prediction operations basedon weight parameters calculated one or more training techniques,including those described herein. In at least one embodiment, eachprocessing cluster 2210 may include, without limitation, any number andtype of processors. In at least one embodiment, deep learningapplication processor 2200 may include any number and type of processingclusters 2200. In at least one embodiment, Inter-Chip Links 2220 arebi-directional. In at least one embodiment, Inter-Chip Links 2220 andInter-Chip Controllers 2230 enable multiple deep learning applicationprocessors 2200 to exchange information, including activationinformation resulting from performing one or more machine learningalgorithms embodied in one or more neural networks. In at least oneembodiment, deep learning application processor 2200 may include anynumber (including zero) and type of ICLs 2220 and ICCs 2230.

In at least one embodiment, HBM2s 2240 provide a total of 32 Gigabytes(GB) of memory. In at least one embodiment, HBM2 2240(i) is associatedwith both memory controller 2242(i) and HBM PHY 2244(i) where “i” is anarbitrary integer. In at least one embodiment, any number of HBM2s 2240may provide any type and total amount of high bandwidth memory and maybe associated with any number (including zero) and type of memorycontrollers 2242 and HBM PHYs 2244. In at least one embodiment, SPI,I²C, GPIO 2260, PCIe Controller and DMA 2270, and/or PCIe 2280 may bereplaced with any number and type of blocks that enable any number andtype of communication standards in any technically feasible fashion.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, deep learning application processor is used to train amachine learning model, such as a neural network, to predict or inferinformation provided to deep learning application processor 2200. In atleast one embodiment, deep learning application processor 2200 is usedto infer or predict information based on a trained machine learningmodel (e.g., neural network) that has been trained by another processoror system or by deep learning application processor 2200. In at leastone embodiment, processor 2200 may be used to perform one or more neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 22 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 23 is a block diagram of a neuromorphic processor 2300, accordingto at least one embodiment. In at least one embodiment, neuromorphicprocessor 2300 may receive one or more inputs from sources external toneuromorphic processor 2300. In at least one embodiment, these inputsmay be transmitted to one or more neurons 2302 within neuromorphicprocessor 2300. In at least one embodiment, neurons 2302 and componentsthereof may be implemented using circuitry or logic, including one ormore arithmetic logic units (ALUs). In at least one embodiment,neuromorphic processor 2300 may include, without limitation, thousandsor millions of instances of neurons 2302, but any suitable number ofneurons 2302 may be used. In at least one embodiment, each instance ofneuron 2302 may include a neuron input 2304 and a neuron output 2306. Inat least one embodiment, neurons 2302 may generate outputs that may betransmitted to inputs of other instances of neurons 2302. For example,in at least one embodiment, neuron inputs 2304 and neuron outputs 2306may be interconnected via synapses 2308.

In at least one embodiment, neurons 2302 and synapses 2308 may beinterconnected such that neuromorphic processor 2300 operates to processor analyze information received by neuromorphic processor 2300. In atleast one embodiment, neurons 2302 may transmit an output pulse (or“fire” or “spike”) when inputs received through neuron input 2304 exceeda threshold. In at least one embodiment, neurons 2302 may sum orintegrate signals received at neuron inputs 2304. For example, in atleast one embodiment, neurons 2302 may be implemented as leakyintegrate-and-fire neurons, wherein if a sum (referred to as a “membranepotential”) exceeds a threshold value, neuron 2302 may generate anoutput (or “fire”) using a transfer function such as a sigmoid orthreshold function. In at least one embodiment, a leakyintegrate-and-fire neuron may sum signals received at neuron inputs 2304into a membrane potential and may also apply a decay factor (or leak) toreduce a membrane potential. In at least one embodiment, a leakyintegrate-and-fire neuron may fire if multiple input signals arereceived at neuron inputs 2304 rapidly enough to exceed a thresholdvalue (i.e., before a membrane potential decays too low to fire). In atleast one embodiment, neurons 2302 may be implemented using circuits orlogic that receive inputs, integrate inputs into a membrane potential,and decay a membrane potential. In at least one embodiment, inputs maybe averaged, or any other suitable transfer function may be used.Furthermore, in at least one embodiment, neurons 2302 may include,without limitation, comparator circuits or logic that generate an outputspike at neuron output 2306 when result of applying a transfer functionto neuron input 2304 exceeds a threshold. In at least one embodiment,once neuron 2302 fires, it may disregard previously received inputinformation by, for example, resetting a membrane potential to 0 oranother suitable default value. In at least one embodiment, oncemembrane potential is reset to 0, neuron 2302 may resume normaloperation after a suitable period of time (or refractory period).

In at least one embodiment, neurons 2302 may be interconnected throughsynapses 2308. In at least one embodiment, synapses 2308 may operate totransmit signals from an output of a first neuron 2302 to an input of asecond neuron 2302. In at least one embodiment, neurons 2302 maytransmit information over more than one instance of synapse 2308. In atleast one embodiment, one or more instances of neuron output 2306 may beconnected, via an instance of synapse 2308, to an instance of neuroninput 2304 in same neuron 2302. In at least one embodiment, an instanceof neuron 2302 generating an output to be transmitted over an instanceof synapse 2308 may be referred to as a “pre-synaptic neuron” withrespect to that instance of synapse 2308. In at least one embodiment, aninstance of neuron 2302 receiving an input transmitted over an instanceof synapse 2308 may be referred to as a “post-synaptic neuron” withrespect to that instance of synapse 2308. Because an instance of neuron2302 may receive inputs from one or more instances of synapse 2308, andmay also transmit outputs over one or more instances of synapse 2308, asingle instance of neuron 2302 may therefore be both a “pre-synapticneuron” and “post-synaptic neuron,” with respect to various instances ofsynapses 2308, in at least one embodiment.

In at least one embodiment, neurons 2302 may be organized into one ormore layers. In at least one embodiment, each instance of neuron 2302may have one neuron output 2306 that may fan out through one or moresynapses 2308 to one or more neuron inputs 2304. In at least oneembodiment, neuron outputs 2306 of neurons 2302 in a first layer 2310may be connected to neuron inputs 2304 of neurons 2302 in a second layer2312. In at least one embodiment, layer 2310 may be referred to as a“feed-forward layer.” In at least one embodiment, each instance ofneuron 2302 in an instance of first layer 2310 may fan out to eachinstance of neuron 2302 in second layer 2312. In at least oneembodiment, first layer 2310 may be referred to as a “fully connectedfeed-forward layer.” In at least one embodiment, each instance of neuron2302 in an instance of second layer 2312 may fan out to fewer than allinstances of neuron 2302 in a third layer 2314. In at least oneembodiment, second layer 2312 may be referred to as a “sparselyconnected feed-forward layer.” In at least one embodiment, neurons 2302in second layer 2312 may fan out to neurons 2302 in multiple otherlayers, including to neurons 2302 also in second layer 2312. In at leastone embodiment, second layer 2312 may be referred to as a “recurrentlayer.” In at least one embodiment, neuromorphic processor 2300 mayinclude, without limitation, any suitable combination of recurrentlayers and feed-forward layers, including, without limitation, bothsparsely connected feed-forward layers and fully connected feed-forwardlayers.

In at least one embodiment, neuromorphic processor 2300 may include,without limitation, a reconfigurable interconnect architecture ordedicated hard-wired interconnects to connect synapse 2308 to neurons2302. In at least one embodiment, neuromorphic processor 2300 mayinclude, without limitation, circuitry or logic that allows synapses tobe allocated to different neurons 2302 as needed based on neural networktopology and neuron fan-in/out. For example, in at least one embodiment,synapses 2308 may be connected to neurons 2302 using an interconnectfabric, such as network-on-chip, or with dedicated connections. In atleast one embodiment, synapse interconnections and components thereofmay be implemented using circuitry or logic.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 23 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 24 is a block diagram of a processing system, according to at leastone embodiment. In at least one embodiment, system 2400 includes one ormore processors 2402 and one or more graphics processors 2408, and maybe a single processor desktop system, a multiprocessor workstationsystem, or a server system having a large number of processors 2402 orprocessor cores 2407. In at least one embodiment, system 2400 is aprocessing platform incorporated within a system-on-a-chip (SoC)integrated circuit for use in mobile, handheld, or embedded devices. Inat least one embodiment, one or more graphics processors 2408 includeone or more graphics cores 1600.

In at least one embodiment, system 2400 can include, or be incorporatedwithin a server-based gaming platform, a game console, including a gameand media console, a mobile gaming console, a handheld game console, oran online game console. In at least one embodiment, system 2400 is amobile phone, a smart phone, a tablet computing device or a mobileInternet device. In at least one embodiment, processing system 2400 canalso include, couple with, or be integrated within a wearable device,such as a smart watch wearable device, a smart eyewear device, anaugmented reality device, or a virtual reality device. In at least oneembodiment, processing system 2400 is a television or set top box devicehaving one or more processors 2402 and a graphical interface generatedby one or more graphics processors 2408.

In at least one embodiment, one or more processors 2402 each include oneor more processor cores 2407 to process instructions which, whenexecuted, perform operations for system and user software. In at leastone embodiment, each of one or more processor cores 2407 is configuredto process a specific instruction sequence 2409. In at least oneembodiment, instruction sequence 2409 may facilitate Complex InstructionSet Computing (CISC), Reduced Instruction Set Computing (RISC), orcomputing via a Very Long Instruction Word (VLIW). In at least oneembodiment, processor cores 2407 may each process a differentinstruction sequence 2409, which may include instructions to facilitateemulation of other instruction sequences. In at least one embodiment,processor core 2407 may also include other processing devices, such aDigital Signal Processor (DSP).

In at least one embodiment, processor 2402 includes a cache memory 2404.In at least one embodiment, processor 2402 can have a single internalcache or multiple levels of internal cache. In at least one embodiment,cache memory is shared among various components of processor 2402. In atleast one embodiment, processor 2402 also uses an external cache (e.g.,a Level-3 (L3) cache or Last Level Cache (LLC)) (not shown), which maybe shared among processor cores 2407 using known cache coherencytechniques. In at least one embodiment, a register file 2406 isadditionally included in processor 2402, which may include differenttypes of registers for storing different types of data (e.g., integerregisters, floating point registers, status registers, and aninstruction pointer register). In at least one embodiment, register file2406 may include general-purpose registers or other registers.

In at least one embodiment, one or more processor(s) 2402 are coupledwith one or more interface bus(es) 2410 to transmit communicationsignals such as address, data, or control signals between processor 2402and other components in system 2400. In at least one embodiment,interface bus 2410 can be a processor bus, such as a version of a DirectMedia Interface (DMI) bus. In at least one embodiment, interface bus2410 is not limited to a DMI bus, and may include one or more PeripheralComponent Interconnect buses (e.g., PCI, PCI Express), memory busses, orother types of interface busses. In at least one embodiment processor(s)2402 include an integrated memory controller 2416 and a platformcontroller hub 2430. In at least one embodiment, memory controller 2416facilitates communication between a memory device and other componentsof system 2400, while platform controller hub (PCH) 2430 providesconnections to I/O devices via a local I/O bus.

In at least one embodiment, a memory device 2420 can be a dynamic randomaccess memory (DRAM) device, a static random access memory (SRAM)device, flash memory device, phase-change memory device, or some othermemory device having suitable performance to serve as process memory. Inat least one embodiment, memory device 2420 can operate as system memoryfor system 2400, to store data 2422 and instructions 2421 for use whenone or more processors 2402 executes an application or process. In atleast one embodiment, memory controller 2416 also couples with anoptional external graphics processor 2412, which may communicate withone or more graphics processors 2408 in processors 2402 to performgraphics and media operations. In at least one embodiment, a displaydevice 2411 can connect to processor(s) 2402. In at least oneembodiment, display device 2411 can include one or more of an internaldisplay device, as in a mobile electronic device or a laptop device, oran external display device attached via a display interface (e.g.,DisplayPort, etc.). In at least one embodiment, display device 2411 caninclude a head mounted display (HMD) such as a stereoscopic displaydevice for use in virtual reality (VR) applications or augmented reality(AR) applications.

In at least one embodiment, platform controller hub 2430 enablesperipherals to connect to memory device 2420 and processor 2402 via ahigh-speed I/O bus. In at least one embodiment, I/O peripherals include,but are not limited to, an audio controller 2446, a network controller2434, a firmware interface 2428, a wireless transceiver 2426, touchsensors 2425, a data storage device 2424 (e.g., hard disk drive, flashmemory, etc.). In at least one embodiment, data storage device 2424 canconnect via a storage interface (e.g., SATA) or via a peripheral bus,such as a Peripheral Component Interconnect bus (e.g., PCI, PCIExpress). In at least one embodiment, touch sensors 2425 can includetouch screen sensors, pressure sensors, or fingerprint sensors. In atleast one embodiment, wireless transceiver 2426 can be a Wi-Fitransceiver, a Bluetooth transceiver, or a mobile network transceiversuch as a 3G, 4G, or Long Term Evolution (LTE) transceiver. In at leastone embodiment, firmware interface 2428 enables communication withsystem firmware, and can be, for example, a unified extensible firmwareinterface (UEFI). In at least one embodiment, network controller 2434can enable a network connection to a wired network. In at least oneembodiment, a high-performance network controller (not shown) coupleswith interface bus 2410. In at least one embodiment, audio controller2446 is a multi-channel high definition audio controller. In at leastone embodiment, system 2400 includes an optional legacy I/O controller2440 for coupling legacy (e.g., Personal System 2 (PS/2)) devices tosystem 2400. In at least one embodiment, platform controller hub 2430can also connect to one or more Universal Serial Bus (USB) controllers2442 connect input devices, such as keyboard and mouse 2443combinations, a camera 2444, or other USB input devices.

In at least one embodiment, an instance of memory controller 2416 andplatform controller hub 2430 may be integrated into a discreet externalgraphics processor, such as external graphics processor 2412. In atleast one embodiment, platform controller hub 2430 and/or memorycontroller 2416 may be external to one or more processor(s) 2402. Forexample, in at least one embodiment, system 2400 can include an externalmemory controller 2416 and platform controller hub 2430, which may beconfigured as a memory controller hub and peripheral controller hubwithin a system chipset that is in communication with processor(s) 2402.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment portions or all of inference and/or training logic 615 may beincorporated into graphics processor 2408. For example, in at least oneembodiment, training and/or inferencing techniques described herein mayuse one or more of ALUs embodied in a 3D pipeline. Moreover, in at leastone embodiment, inferencing and/or training operations described hereinmay be done using logic other than logic illustrated in FIG. 6A or 6B.In at least one embodiment, weight parameters may be stored in on-chipor off-chip memory and/or registers (shown or not shown) that configureALUs of graphics processor 2408 to perform one or more machine learningalgorithms, neural network architectures, use cases, or trainingtechniques described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 24 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 25 is a block diagram of a processor 2500 having one or moreprocessor cores 2502A-2502N, an integrated memory controller 2514, andan integrated graphics processor 2508, according to at least oneembodiment. In at least one embodiment, processor 2500 can includeadditional cores up to and including additional core 2502N representedby dashed lined boxes. In at least one embodiment, each of processorcores 2502A-2502N includes one or more internal cache units 2504A-2504N.In at least one embodiment, each processor core also has access to oneor more shared cached units 2506. In at least one embodiment, graphicsprocessor 2508 includes one or more graphics cores 1600.

In at least one embodiment, internal cache units 2504A-2504N and sharedcache units 2506 represent a cache memory hierarchy within processor2500. In at least one embodiment, cache memory units 2504A-2504N mayinclude at least one level of instruction and data cache within eachprocessor core and one or more levels of shared mid-level cache, such asa Level 2 (L2), Level 3 (L3), Level 4 (L4), or other levels of cache,where a highest level of cache before external memory is classified asan LLC. In at least one embodiment, cache coherency logic maintainscoherency between various cache units 2506 and 2504A-2504N.

In at least one embodiment, processor 2500 may also include a set of oneor more bus controller units 2516 and a system agent core 2510. In atleast one embodiment, bus controller units 2516 manage a set ofperipheral buses, such as one or more PCI or PCI express busses. In atleast one embodiment, system agent core 2510 provides managementfunctionality for various processor components. In at least oneembodiment, system agent core 2510 includes one or more integratedmemory controllers 2514 to manage access to various external memorydevices (not shown).

In at least one embodiment, one or more of processor cores 2502A-2502Ninclude support for simultaneous multi-threading. In at least oneembodiment, system agent core 2510 includes components for coordinatingand operating cores 2502A-2502N during multi-threaded processing. In atleast one embodiment, system agent core 2510 may additionally include apower control unit (PCU), which includes logic and components toregulate one or more power states of processor cores 2502A-2502N andgraphics processor 2508.

In at least one embodiment, processor 2500 additionally includesgraphics processor 2508 to execute graphics processing operations. In atleast one embodiment, graphics processor 2508 couples with shared cacheunits 2506, and system agent core 2510, including one or more integratedmemory controllers 2514. In at least one embodiment, system agent core2510 also includes a display controller 2511 to drive graphics processoroutput to one or more coupled displays. In at least one embodiment,display controller 2511 may also be a separate module coupled withgraphics processor 2508 via at least one interconnect, or may beintegrated within graphics processor 2508.

In at least one embodiment, a ring-based interconnect unit 2512 is usedto couple internal components of processor 2500. In at least oneembodiment, an alternative interconnect unit may be used, such as apoint-to-point interconnect, a switched interconnect, or othertechniques. In at least one embodiment, graphics processor 2508 coupleswith ring interconnect 2512 via an I/O link 2513.

In at least one embodiment, I/O link 2513 represents at least one ofmultiple varieties of I/O interconnects, including an on package I/Ointerconnect which facilitates communication between various processorcomponents and a high-performance embedded memory module 2518, such asan eDRAM module. In at least one embodiment, each of processor cores2502A-2502N and graphics processor 2508 use embedded memory module 2518as a shared Last Level Cache.

In at least one embodiment, processor cores 2502A-2502N are homogeneouscores executing a common instruction set architecture. In at least oneembodiment, processor cores 2502A-2502N are heterogeneous in terms ofinstruction set architecture (ISA), where one or more of processor cores2502A-2502N execute a common instruction set, while one or more othercores of processor cores 2502A-2502N executes a subset of a commoninstruction set or a different instruction set. In at least oneembodiment, processor cores 2502A-2502N are heterogeneous in terms ofmicroarchitecture, where one or more cores having a relatively higherpower consumption couple with one or more power cores having a lowerpower consumption. In at least one embodiment, processor 2500 can beimplemented on one or more chips or as an SoC integrated circuit.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment portions or all of inference and/or training logic 615 may beincorporated into graphics processor 2508. For example, in at least oneembodiment, training and/or inferencing techniques described herein mayuse one or more of ALUs embodied in a 3D pipeline, graphics core(s)2502, shared function logic, or other logic in FIG. 25 . Moreover, in atleast one embodiment, inferencing and/or training operations describedherein may be done using logic other than logic illustrated in FIG. 6Aor 6B. In at least one embodiment, weight parameters may be stored inon-chip or off-chip memory and/or registers (shown or not shown) thatconfigure ALUs of processor 2500 to perform one or more machine learningalgorithms, neural network architectures, use cases, or trainingtechniques described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 25 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 26 is a block diagram of a graphics processor 2600, which may be adiscrete graphics processing unit, or may be a graphics processorintegrated with a plurality of processing cores. In at least oneembodiment, graphics processor 2600 communicates via a memory mapped I/Ointerface to registers on graphics processor 2600 and with commandsplaced into memory. In at least one embodiment, graphics processor 2600includes a memory interface 2614 to access memory. In at least oneembodiment, memory interface 2614 is an interface to local memory, oneor more internal caches, one or more shared external caches, and/or tosystem memory. In at least one embodiment, graphics processor 2600includes graphics core 1600.

In at least one embodiment, graphics processor 2600 also includes adisplay controller 2602 to drive display output data to a display device2620. In at least one embodiment, display controller 2602 includeshardware for one or more overlay planes for display device 2620 andcomposition of multiple layers of video or user interface elements. Inat least one embodiment, display device 2620 can be an internal orexternal display device. In at least one embodiment, display device 2620is a head mounted display device, such as a virtual reality (VR) displaydevice or an augmented reality (AR) display device. In at least oneembodiment, graphics processor 2600 includes a video codec engine 2606to encode, decode, or transcode media to, from, or between one or moremedia encoding formats, including, but not limited to Moving PictureExperts Group (MPEG) formats such as MPEG-2, Advanced Video Coding (AVC)formats such as H.264/MPEG-4 AVC, as well as the Society of MotionPicture & Television Engineers (SMPTE) 421M/VC-1, and Joint PhotographicExperts Group (JPEG) formats such as JPEG, and Motion JPEG (MJPEG)formats.

In at least one embodiment, graphics processor 2600 includes a blockimage transfer (BLIT) engine 2604 to perform two-dimensional (2D)rasterizer operations including, for example, bit-boundary blocktransfers. However, in at least one embodiment, 2D graphics operationsare performed using one or more components of a graphics processingengine (GPE) 2610. In at least one embodiment, GPE 2610 is a computeengine for performing graphics operations, including three-dimensional(3D) graphics operations and media operations.

In at least one embodiment, GPE 2610 includes a 3D pipeline 2612 forperforming 3D operations, such as rendering three-dimensional images andscenes using processing functions that act upon 3D primitive shapes(e.g., rectangle, triangle, etc.). In at least one embodiment, 3Dpipeline 2612 includes programmable and fixed function elements thatperform various tasks and/or spawn execution threads to a 3D/Mediasub-system 2615. While 3D pipeline 2612 can be used to perform mediaoperations, in at least one embodiment, GPE 2610 also includes a mediapipeline 2616 that is used to perform media operations, such as videopost-processing and image enhancement.

In at least one embodiment, media pipeline 2616 includes fixed functionor programmable logic units to perform one or more specialized mediaoperations, such as video decode acceleration, video de-interlacing, andvideo encode acceleration in place of, or on behalf of, video codecengine 2606. In at least one embodiment, media pipeline 2616additionally includes a thread spawning unit to spawn threads forexecution on 3D/Media sub-system 2615. In at least one embodiment,spawned threads perform computations for media operations on one or moregraphics execution units included in 3D/Media sub-system 2615.

In at least one embodiment, 3D/Media subsystem 2615 includes logic forexecuting threads spawned by 3D pipeline 2612 and media pipeline 2616.In at least one embodiment, 3D pipeline 2612 and media pipeline 2616send thread execution requests to 3D/Media subsystem 2615, whichincludes thread dispatch logic for arbitrating and dispatching variousrequests to available thread execution resources. In at least oneembodiment, execution resources include an array of graphics executionunits to process 3D and media threads. In at least one embodiment,3D/Media subsystem 2615 includes one or more internal caches for threadinstructions and data. In at least one embodiment, subsystem 2615 alsoincludes shared memory, including registers and addressable memory, toshare data between threads and to store output data.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment portions or all of inference and/or training logic 615 may beincorporated into graphics processor 2600. For example, in at least oneembodiment, training and/or inferencing techniques described herein mayuse one or more of ALUs embodied in 3D pipeline 2612. Moreover, in atleast one embodiment, inferencing and/or training operations describedherein may be done using logic other than logic illustrated in FIG. 6Aor 6B. In at least one embodiment, weight parameters may be stored inon-chip or off-chip memory and/or registers (shown or not shown) thatconfigure ALUs of graphics processor 2600 to perform one or more machinelearning algorithms, neural network architectures, use cases, ortraining techniques described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 26 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 27 is a block diagram of a graphics processing engine 2710 of agraphics processor in accordance with at least one embodiment. In atleast one embodiment, graphics processing engine (GPE) 2710 is a versionof GPE 2610 shown in FIG. 26 . In at least one embodiment, a mediapipeline 2716 is optional and may not be explicitly included within GPE2710. In at least one embodiment, a separate media and/or imageprocessor is coupled to GPE 2710.

In at least one embodiment, GPE 2710 is coupled to or includes a commandstreamer 2703, which provides a command stream to a 3D pipeline 2712and/or media pipeline 2716. In at least one embodiment, command streamer2703 is coupled to memory, which can be system memory, or one or more ofinternal cache memory and shared cache memory. In at least oneembodiment, command streamer 2703 receives commands from memory andsends commands to 3D pipeline 2712 and/or media pipeline 2716. In atleast one embodiment, commands are instructions, primitives, ormicro-operations fetched from a ring buffer, which stores commands for3D pipeline 2712 and media pipeline 2716. In at least one embodiment, aring buffer can additionally include batch command buffers storingbatches of multiple commands. In at least one embodiment, commands for3D pipeline 2712 can also include references to data stored in memory,such as, but not limited to, vertex and geometry data for 3D pipeline2712 and/or image data and memory objects for media pipeline 2716. In atleast one embodiment, 3D pipeline 2712 and media pipeline 2716 processcommands and data by performing operations or by dispatching one or moreexecution threads to a graphics core array 2714. In at least oneembodiment, graphics core array 2714 includes one or more blocks ofgraphics cores (e.g., graphics core(s) 2715A, graphics core(s) 2715B),each block including one or more graphics cores. In at least oneembodiment, graphics core(s) 2715A, 2715B may be referred to asexecution units (“EUs”). In at least one embodiment, each graphics coreincludes a set of graphics execution resources that includesgeneral-purpose and graphics specific execution logic to performgraphics and compute operations, as well as fixed function textureprocessing and/or machine learning and artificial intelligenceacceleration logic, including inference and/or training logic 615 inFIG. 6A and FIG. 6B.

In at least one embodiment, 3D pipeline 2712 includes fixed function andprogrammable logic to process one or more shader programs, such asvertex shaders, geometry shaders, pixel shaders, fragment shaders,compute shaders, or other shader programs, by processing instructionsand dispatching execution threads to graphics core array 2714. In atleast one embodiment, graphics core array 2714 provides a unified blockof execution resources for use in processing shader programs. In atleast one embodiment, a multi-purpose execution logic (e.g., executionunits) within graphics core(s) 2715A-2715B of graphic core array 2714includes support for various 3D API shader languages and can executemultiple simultaneous execution threads associated with multipleshaders.

In at least one embodiment, graphics core array 2714 also includesexecution logic to perform media functions, such as video and/or imageprocessing. In at least one embodiment, execution units additionallyinclude general-purpose logic that is programmable to perform parallelgeneral-purpose computational operations, in addition to graphicsprocessing operations.

In at least one embodiment, output data generated by threads executingon graphics core array 2714 can output data to memory in a unifiedreturn buffer (URB) 2718. In at least one embodiment, URB 2718 can storedata for multiple threads. In at least one embodiment, URB 2718 may beused to send data between different threads executing on graphics corearray 2714. In at least one embodiment, URB 2718 may additionally beused for synchronization between threads on graphics core array 2714 andfixed function logic within shared function logic 2720.

In at least one embodiment, graphics core array 2714 is scalable, suchthat graphics core array 2714 includes a variable number of graphicscores, each having a variable number of execution units based on atarget power and performance level of GPE 2710. In at least oneembodiment, execution resources are dynamically scalable, such thatexecution resources may be enabled or disabled as needed.

In at least one embodiment, graphics core array 2714 is coupled toshared function logic 2720 that includes multiple resources that areshared between graphics cores in graphics core array 2714. In at leastone embodiment, shared functions performed by shared function logic 2720are embodied in hardware logic units that provide specializedsupplemental functionality to graphics core array 2714. In at least oneembodiment, shared function logic 2720 includes but is not limited to asampler unit 2721, a math unit 2722, and inter-thread communication(ITC) logic 2723. In at least one embodiment, one or more cache(s) 2725are included in, or coupled to, shared function logic 2720.

In at least one embodiment, a shared function is used if demand for aspecialized function is insufficient for inclusion within graphics corearray 2714. In at least one embodiment, a single instantiation of aspecialized function is used in shared function logic 2720 and sharedamong other execution resources within graphics core array 2714. In atleast one embodiment, specific shared functions within shared functionlogic 2720 that are used extensively by graphics core array 2714 may beincluded within shared function logic 2726 within graphics core array2714. In at least one embodiment, shared function logic 2726 withingraphics core array 2714 can include some or all logic within sharedfunction logic 2720. In at least one embodiment, all logic elementswithin shared function logic 2720 may be duplicated within sharedfunction logic 2726 of graphics core array 2714. In at least oneembodiment, shared function logic 2720 is excluded in favor of sharedfunction logic 2726 within graphics core array 2714.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment portions or all of inference and/or training logic 615 may beincorporated into graphics processor 2710. For example, in at least oneembodiment, training and/or inferencing techniques described herein mayuse one or more of ALUs embodied in 3D pipeline 2712, graphics core(s)2715, shared function logic 2726, shared function logic 2720, or otherlogic in FIG. 27 . Moreover, in at least one embodiment, inferencingand/or training operations described herein may be done using logicother than logic illustrated in FIG. 6A or 6B. In at least oneembodiment, weight parameters may be stored in on-chip or off-chipmemory and/or registers (shown or not shown) that configure ALUs ofgraphics processor 2710 to perform one or more machine learningalgorithms, neural network architectures, use cases, or trainingtechniques described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 27 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 28 is a block diagram of hardware logic of a graphics processorcore 2800, according to at least one embodiment described herein. In atleast one embodiment, graphics processor core 2800 includes graphicscore 1600. In at least one embodiment, graphics processor core 2800 isincluded within a graphics core array. In at least one embodiment,graphics processor core 2800, sometimes referred to as a core slice, canbe one or multiple graphics cores within a modular graphics processor.In at least one embodiment, graphics processor core 2800 is exemplary ofone graphics core slice, and a graphics processor as described hereinmay include multiple graphics core slices based on target power andperformance envelopes. In at least one embodiment, each graphics core2800 can include a fixed function block 2830 coupled with multiplesub-cores 2801A-2801F, also referred to as sub-slices, that includemodular blocks of general-purpose and fixed function logic.

In at least one embodiment, fixed function block 2830 includes ageometry and fixed function pipeline 2836 that can be shared by allsub-cores in graphics processor 2800, for example, in lower performanceand/or lower power graphics processor implementations. In at least oneembodiment, geometry and fixed function pipeline 2836 includes a 3Dfixed function pipeline, a video front-end unit, a thread spawner andthread dispatcher, and a unified return buffer manager, which managesunified return buffers.

In at least one embodiment, fixed function block 2830 also includes agraphics SoC interface 2837, a graphics microcontroller 2838, and amedia pipeline 2839. In at least one embodiment, graphics SoC interface2837 provides an interface between graphics core 2800 and otherprocessor cores within a system on a chip integrated circuit. In atleast one embodiment, graphics microcontroller 2838 is a programmablesub-processor that is configurable to manage various functions ofgraphics processor 2800, including thread dispatch, scheduling, andpre-emption. In at least one embodiment, media pipeline 2839 includeslogic to facilitate decoding, encoding, pre-processing, and/orpost-processing of multimedia data, including image and video data. Inat least one embodiment, media pipeline 2839 implements media operationsvia requests to compute or sampling logic within sub-cores 2801A-2801F.

In at least one embodiment, SoC interface 2837 enables graphics core2800 to communicate with general-purpose application processor cores(e.g., CPUs) and/or other components within an SoC, including memoryhierarchy elements such as a shared last level cache memory, system RAM,and/or embedded on-chip or on-package DRAM. In at least one embodiment,SoC interface 2837 can also enable communication with fixed functiondevices within an SoC, such as camera imaging pipelines, and enables useof and/or implements global memory atomics that may be shared betweengraphics core 2800 and CPUs within an SoC. In at least one embodiment,graphics SoC interface 2837 can also implement power management controlsfor graphics processor core 2800 and enable an interface between a clockdomain of graphics processor core 2800 and other clock domains within anSoC. In at least one embodiment, SoC interface 2837 enables receipt ofcommand buffers from a command streamer and global thread dispatcherthat are configured to provide commands and instructions to each of oneor more graphics cores within a graphics processor. In at least oneembodiment, commands and instructions can be dispatched to mediapipeline 2839, when media operations are to be performed, or a geometryand fixed function pipeline (e.g., geometry and fixed function pipeline2836, and/or a geometry and fixed function pipeline 2814) when graphicsprocessing operations are to be performed.

In at least one embodiment, graphics microcontroller 2838 can beconfigured to perform various scheduling and management tasks forgraphics core 2800. In at least one embodiment, graphics microcontroller2838 can perform graphics and/or compute workload scheduling on variousgraphics parallel engines within execution unit (EU) arrays 2802A-2802F,2804A-2804F within sub-cores 2801A-2801F. In at least one embodiment,host software executing on a CPU core of an SoC including graphics core2800 can submit workloads to one of multiple graphic processor paths,which invokes a scheduling operation on an appropriate graphics engine.In at least one embodiment, scheduling operations include determiningwhich workload to run next, submitting a workload to a command streamer,pre-empting existing workloads running on an engine, monitoring progressof a workload, and notifying host software when a workload is complete.In at least one embodiment, graphics microcontroller 2838 can alsofacilitate low-power or idle states for graphics core 2800, providinggraphics core 2800 with an ability to save and restore registers withingraphics core 2800 across low-power state transitions independently froman operating system and/or graphics driver software on a system.

In at least one embodiment, graphics core 2800 may have greater than orfewer than illustrated sub-cores 2801A-2801F, up to N modular sub-cores.For each set of N sub-cores, in at least one embodiment, graphics core2800 can also include shared function logic 2810, shared and/or cachememory 2812, geometry/fixed function pipeline 2814, as well asadditional fixed function logic 2816 to accelerate various graphics andcompute processing operations. In at least one embodiment, sharedfunction logic 2810 can include logic units (e.g., sampler, math, and/orinter-thread communication logic) that can be shared by each N sub-coreswithin graphics core 2800. In at least one embodiment, shared and/orcache memory 2812 can be a last-level cache for N sub-cores 2801A-2801Fwithin graphics core 2800 and can also serve as shared memory that isaccessible by multiple sub-cores. In at least one embodiment,geometry/fixed function pipeline 2814 can be included instead ofgeometry/fixed function pipeline 2836 within fixed function block 2830and can include similar logic units.

In at least one embodiment, graphics core 2800 includes additional fixedfunction logic 2816 that can include various fixed function accelerationlogic for use by graphics core 2800. In at least one embodiment,additional fixed function logic 2816 includes an additional geometrypipeline for use in position-only shading. In position-only shading, atleast two geometry pipelines exist, whereas in a full geometry pipelinewithin geometry and fixed function pipelines 2814, 2836, and a cullpipeline, which is an additional geometry pipeline that may be includedwithin additional fixed function logic 2816. In at least one embodiment,a cull pipeline is a trimmed down version of a full geometry pipeline.In at least one embodiment, a full pipeline and a cull pipeline canexecute different instances of an application, each instance having aseparate context. In at least one embodiment, position only shading canhide long cull runs of discarded triangles, enabling shading to becompleted earlier in some instances. For example, in at least oneembodiment, cull pipeline logic within additional fixed function logic2816 can execute position shaders in parallel with a main applicationand generally generates critical results faster than a full pipeline, asa cull pipeline fetches and shades position attributes of vertices,without performing rasterization and rendering of pixels to a framebuffer. In at least one embodiment, a cull pipeline can use generatedcritical results to compute visibility information for all triangleswithout regard to whether those triangles are culled. In at least oneembodiment, a full pipeline (which in this instance may be referred toas a replay pipeline) can consume visibility information to skip culledtriangles to shade only visible triangles that are finally passed to arasterization phase.

In at least one embodiment, additional fixed function logic 2816 canalso include machine-learning acceleration logic, such as fixed functionmatrix multiplication logic, for implementations including optimizationsfor machine learning training or inferencing.

In at least one embodiment, within each graphics sub-core 2801A-2801Fincludes a set of execution resources that may be used to performgraphics, media, and compute operations in response to requests bygraphics pipeline, media pipeline, or shader programs. In at least oneembodiment, graphics sub-cores 2801A-2801F include multiple EU arrays2802A-2802F, 2804A-2804F, thread dispatch and inter-thread communication(TD/IC) logic 2803A-2803F, a 3D (e.g., texture) sampler 2805A-2805F, amedia sampler 2806A-2806F, a shader processor 2807A-2807F, and sharedlocal memory (SLM) 2808A-2808F. In at least one embodiment, EU arrays2802A-2802F, 2804A-2804F each include multiple execution units, whichare general-purpose graphics processing units capable of performingfloating-point and integer/fixed-point logic operations in service of agraphics, media, or compute operation, including graphics, media, orcompute shader programs. In at least one embodiment, TD/IC logic2803A-2803F performs local thread dispatch and thread control operationsfor execution units within a sub-core and facilitates communicationbetween threads executing on execution units of a sub-core. In at leastone embodiment, 3D samplers 2805A-2805F can read texture or other 3Dgraphics related data into memory. In at least one embodiment, 3Dsamplers can read texture data differently based on a configured samplestate and texture format associated with a given texture. In at leastone embodiment, media samplers 2806A-2806F can perform similar readoperations based on a type and format associated with media data. In atleast one embodiment, each graphics sub-core 2801A-2801F can alternatelyinclude a unified 3D and media sampler. In at least one embodiment,threads executing on execution units within each of sub-cores2801A-2801F can make use of shared local memory 2808A-2808F within eachsub-core, to enable threads executing within a thread group to executeusing a common pool of on-chip memory.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, portions or all of inference and/or training logic 615 maybe incorporated into graphics processor 2800. For example, in at leastone embodiment, training and/or inferencing techniques described hereinmay use one or more of ALUs embodied in a 3D pipeline, graphicsmicrocontroller 2838, geometry and fixed function pipeline 2814 and2836, or other logic in FIG. 28 . Moreover, in at least one embodiment,inferencing and/or training operations described herein may be doneusing logic other than logic illustrated in FIG. 6A or 6B. In at leastone embodiment, weight parameters may be stored in on-chip or off-chipmemory and/or registers (shown or not shown) that configure ALUs ofgraphics processor 2800 to perform one or more machine learningalgorithms, neural network architectures, use cases, or trainingtechniques described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 28 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIGS. 29A-29B illustrate thread execution logic 2900 including an arrayof processing elements of a graphics processor core according to atleast one embodiment. FIG. 29A illustrates at least one embodiment, inwhich thread execution logic 2900 is used. FIG. 29B illustratesexemplary internal details of a graphics execution unit 2908, accordingto at least one embodiment.

As illustrated in FIG. 29A, in at least one embodiment, thread executionlogic 2900 includes a shader processor 2902, a thread dispatcher 2904,an instruction cache 2906, a scalable execution unit array including aplurality of execution units 2907A-2907N and 2908A-2908N, a sampler2910, a data cache 2912, and a data port 2914. In at least oneembodiment, a scalable execution unit array can dynamically scale byenabling or disabling one or more execution units (e.g., any ofexecution unit 2908A-N or 2907A-N) based on computational requirementsof a workload, for example. In at least one embodiment, scalableexecution units are interconnected via an interconnect fabric that linksto each execution unit. In at least one embodiment, thread executionlogic 2900 includes one or more connections to memory, such as systemmemory or cache memory, through one or more of instruction cache 2906,data port 2914, sampler 2910, and execution units 2907 or 2908. In atleast one embodiment, each execution unit (e.g., 2907A) is a stand-aloneprogrammable general-purpose computational unit that is capable ofexecuting multiple simultaneous hardware threads while processingmultiple data elements in parallel for each thread. In at least oneembodiment, array of execution units 2907 and/or 2908 is scalable toinclude any number individual execution units.

In at least one embodiment, execution units 2907 and/or 2908 areprimarily used to execute shader programs. In at least one embodiment,shader processor 2902 can process various shader programs and dispatchexecution threads associated with shader programs via a threaddispatcher 2904. In at least one embodiment, thread dispatcher 2904includes logic to arbitrate thread initiation requests from graphics andmedia pipelines and instantiate requested threads on one or moreexecution units in execution units 2907 and/or 2908. For example, in atleast one embodiment, a geometry pipeline can dispatch vertex,tessellation, or geometry shaders to thread execution logic forprocessing. In at least one embodiment, thread dispatcher 2904 can alsoprocess runtime thread spawning requests from executing shader programs.

In at least one embodiment, execution units 2907 and/or 2908 support aninstruction set that includes native support for many standard 3Dgraphics shader instructions, such that shader programs from graphicslibraries (e.g., Direct 3D and OpenGL) are executed with a minimaltranslation. In at least one embodiment, execution units support vertexand geometry processing (e.g., vertex programs, geometry programs,and/or vertex shaders), pixel processing (e.g., pixel shaders, fragmentshaders) and general-purpose processing (e.g., compute and mediashaders). In at least one embodiment, each of execution units 2907and/or 2908, which include one or more arithmetic logic units (ALUs), iscapable of multi-issue single instruction multiple data (SIMD) executionand multi-threaded operation enables an efficient execution environmentdespite higher latency memory accesses. In at least one embodiment, eachhardware thread within each execution unit has a dedicatedhigh-bandwidth register file and associated independent thread-state. Inat least one embodiment, execution is multi-issue per clock to pipelinescapable of integer, single and double precision floating pointoperations, SIMD branch capability, logical operations, transcendentaloperations, and other miscellaneous operations. In at least oneembodiment, while waiting for data from memory or one of sharedfunctions, dependency logic within execution units 2907 and/or 2908causes a waiting thread to sleep until requested data has been returned.In at least one embodiment, while an awaiting thread is sleeping,hardware resources may be devoted to processing other threads. Forexample, in at least one embodiment, during a delay associated with avertex shader operation, an execution unit can perform operations for apixel shader, fragment shader, or another type of shader program,including a different vertex shader.

In at least one embodiment, each execution unit in execution units 2907and/or 2908 operates on arrays of data elements. In at least oneembodiment, a number of data elements is an “execution size,” or numberof channels for an instruction. In at least one embodiment, an executionchannel is a logical unit of execution for data element access, masking,and flow control within instructions. In at least one embodiment, anumber of channels may be independent of a number of physical arithmeticlogic units (ALUs) or floating point units (FPUs) for a particulargraphics processor. In at least one embodiment, execution units 2907and/or 2908 support integer and floating-point data types.

In at least one embodiment, an execution unit instruction set includesSIMD instructions. In at least one embodiment, various data elements canbe stored as a packed data type in a register and execution unit willprocess various elements based on data size of elements. For example, inat least one embodiment, when operating on a 256-bit wide vector, 256bits of a vector are stored in a register and an execution unit operateson a vector as four separate 64-bit packed data elements (Quad-Word (QW)size data elements), eight separate 32-bit packed data elements (DoubleWord (DW) size data elements), sixteen separate 16-bit packed dataelements (Word (W) size data elements), or thirty-two separate 8-bitdata elements (byte (B) size data elements). However, in at least oneembodiment, different vector widths and register sizes are possible.

In at least one embodiment, one or more execution units can be combinedinto a fused execution unit 2909A-2909N having thread control logic(2911A-2911N) that is common to fused EUs such as execution unit 2907Afused with execution unit 2908A into fused execution unit 2909A. In atleast one embodiment, multiple EUs can be fused into an EU group. In atleast one embodiment, each EU in a fused EU group can be configured toexecute a separate SIMD hardware thread, with a number of EUs in a fusedEU group possibly varying according to various embodiments. In at leastone embodiment, various SIMD widths can be performed per-EU, includingbut not limited to SIMD8, SIMD16, and SIMD32. In at least oneembodiment, each fused graphics execution unit 2909A-2909N includes atleast two execution units. For example, in at least one embodiment,fused execution unit 2909A includes a first EU 2907A, second EU 2908A,and thread control logic 2911A that is common to first EU 2907A andsecond EU 2908A. In at least one embodiment, thread control logic 2911Acontrols threads executed on fused graphics execution unit 2909A,allowing each EU within fused execution units 2909A-2909N to executeusing a common instruction pointer register.

In at least one embodiment, one or more internal instruction caches(e.g., 2906) are included in thread execution logic 2900 to cache threadinstructions for execution units. In at least one embodiment, one ormore data caches (e.g., 2912) are included to cache thread data duringthread execution. In at least one embodiment, sampler 2910 is includedto provide texture sampling for 3D operations and media sampling formedia operations. In at least one embodiment, sampler 2910 includesspecialized texture or media sampling functionality to process textureor media data during sampling process before providing sampled data toan execution unit.

During execution, in at least one embodiment, graphics and mediapipelines send thread initiation requests to thread execution logic 2900via thread spawning and dispatch logic. In at least one embodiment, oncea group of geometric objects has been processed and rasterized intopixel data, pixel processor logic (e.g., pixel shader logic, fragmentshader logic, etc.) within shader processor 2902 is invoked to furthercompute output information and cause results to be written to outputsurfaces (e.g., color buffers, depth buffers, stencil buffers, etc.). Inat least one embodiment, a pixel shader or a fragment shader calculatesvalues of various vertex attributes that are to be interpolated across arasterized object. In at least one embodiment, pixel processor logicwithin shader processor 2902 then executes an application programminginterface (API)-supplied pixel or fragment shader program. In at leastone embodiment, to execute a shader program, shader processor 2902dispatches threads to an execution unit (e.g., 2908A) via threaddispatcher 2904. In at least one embodiment, shader processor 2902 usestexture sampling logic in sampler 2910 to access texture data in texturemaps stored in memory. In at least one embodiment, arithmetic operationson texture data and input geometry data compute pixel color data foreach geometric fragment, or discards one or more pixels from furtherprocessing.

In at least one embodiment, data port 2914 provides a memory accessmechanism for thread execution logic 2900 to output processed data tomemory for further processing on a graphics processor output pipeline.In at least one embodiment, data port 2914 includes or couples to one ormore cache memories (e.g., data cache 2912) to cache data for memoryaccess via a data port.

As illustrated in FIG. 29B, in at least one embodiment, a graphicsexecution unit 2908 can include an instruction fetch unit 2937, ageneral register file array (GRF) 2924, an architectural register filearray (ARF) 2926, a thread arbiter 2922, a send unit 2930, a branch unit2932, a set of SIMD floating point units (FPUs) 2934, and a set ofdedicated integer SIMD ALUs 2935. In at least one embodiment, GRF 2924and ARF 2926 includes a set of general register files and architectureregister files associated with each simultaneous hardware thread thatmay be active in graphics execution unit 2908. In at least oneembodiment, per thread architectural state is maintained in ARF 2926,while data used during thread execution is stored in GRF 2924. In atleast one embodiment, execution state of each thread, includinginstruction pointers for each thread, can be held in thread-specificregisters in ARF 2926.

In at least one embodiment, graphics execution unit 2908 has anarchitecture that is a combination of Simultaneous Multi-Threading (SMT)and fine-grained Interleaved Multi-Threading (IMT). In at least oneembodiment, architecture has a modular configuration that can befine-tuned at design time based on a target number of simultaneousthreads and number of registers per execution unit, where execution unitresources are divided across logic used to execute multiple simultaneousthreads.

In at least one embodiment, graphics execution unit 2908 can co-issuemultiple instructions, which may each be different instructions. In atleast one embodiment, thread arbiter 2922 of graphics execution unitthread 2908 can dispatch instructions to one of send unit 2930, branchunit 2932, or SIMD FPU(s) 2934 for execution. In at least oneembodiment, each execution thread can access 128 general-purposeregisters within GRF 2924, where each register can store 32 bytes,accessible as a SIMD 8-element vector of 32-bit data elements. In atleast one embodiment, each execution unit thread has access to 4kilobytes within GRF 2924, although embodiments are not so limited, andgreater or fewer register resources may be provided in otherembodiments. In at least one embodiment, up to seven threads can executesimultaneously, although a number of threads per execution unit can alsovary according to embodiments. In at least one embodiment, in whichseven threads may access 4 kilobytes, GRF 2924 can store a total of 28kilobytes. In at least one embodiment, flexible addressing modes canpermit registers to be addressed together to build effectively widerregisters or to represent strided rectangular block data structures.

In at least one embodiment, memory operations, sampler operations, andother longer-latency system communications are dispatched via “send”instructions that are executed by message passing to send unit 2930. Inat least one embodiment, branch instructions are dispatched to branchunit 2932 to facilitate SIMD divergence and eventual convergence.

In at least one embodiment, graphics execution unit 2908 includes one ormore SIMD floating point units (FPU(s)) 2934 to perform floating-pointoperations. In at least one embodiment, FPU(s) 2934 also support integercomputation. In at least one embodiment, FPU(s) 2934 can SIMD execute upto M number of 32-bit floating-point (or integer) operations, or SIMDexecute up to 2M 16-bit integer or 16-bit floating-point operations. Inat least one embodiment, at least one FPU provides extended mathcapability to support high-throughput transcendental math functions anddouble precision 64-bit floating-point. In at least one embodiment, aset of 8-bit integer SIMD ALUs 2935 are also present, and may bespecifically optimized to perform operations associated with machinelearning computations.

In at least one embodiment, arrays of multiple instances of graphicsexecution unit 2908 can be instantiated in a graphics sub-core grouping(e.g., a sub-slice). In at least one embodiment, execution unit 2908 canexecute instructions across a plurality of execution channels. In atleast one embodiment, each thread executed on graphics execution unit2908 is executed on a different channel.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, portions or all of inference and/or training logic 615 maybe incorporated into thread execution logic 2900. Moreover, in at leastone embodiment, inferencing and/or training operations described hereinmay be done using logic other than logic illustrated in FIG. 6A or 6B.In at least one embodiment, weight parameters may be stored in on-chipor off-chip memory and/or registers (shown or not shown) that configureALUs thread of execution logic 2900 to perform one or more machinelearning algorithms, neural network architectures, use cases, ortraining techniques described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIGS. 29A, B and may be configured to receive sensor inputs frommultiple sensors and may be trained to infer a coolant requirement. Inat least one embodiment, an inference and/or training logic 615 may beable to infer this using information from historical coolingrequirements and of historical sensor inputs. In at least oneembodiment, an inference and/or training logic 615 may make an inferenceof a change in a cooling requirement. In at least one embodiment, sensorinputs may be correlated to classes of different cooling requirements ofeach of different sensor inputs. In at least one embodiment, a newsensor input classifying within a class of such different sensor inputsmay indicate a cooling requirement, or a change thereof.

FIG. 30 illustrates a parallel processing unit (“PPU”) 3000, accordingto at least one embodiment. In at least one embodiment, PPU 3000 isconfigured with machine-readable code that, if executed by PPU 3000,causes PPU 3000 to perform some or all of processes and techniquesdescribed throughout this disclosure. In at least one embodiment, PPU3000 is a multi-threaded processor that is implemented on one or moreintegrated circuit devices and that utilizes multithreading as alatency-hiding technique designed to process computer-readableinstructions (also referred to as machine-readable instructions orsimply instructions) on multiple threads in parallel. In at least oneembodiment, PPU 3000 includes one or more graphics cores 1600 In atleast one embodiment, a thread refers to a thread of execution and is aninstantiation of a set of instructions configured to be executed by PPU3000. In at least one embodiment, PPU 3000 is a graphics processing unit(“GPU”) configured to implement a graphics rendering pipeline forprocessing three-dimensional (“3D”) graphics data in order to generatetwo-dimensional (“2D”) image data for display on a display device suchas a liquid crystal display (“LCD”) device. In at least one embodiment,PPU 3000 is utilized to perform computations such as linear algebraoperations and machine-learning operations. FIG. 30 illustrates anexample parallel processor for illustrative purposes only and should beconstrued as a non-limiting example of processor architecturescontemplated within scope of this disclosure and that any suitableprocessor may be employed to supplement and/or substitute for same.

In at least one embodiment, one or more PPUs 3000 are configured toaccelerate High Performance Computing (“HPC”), data center, and machinelearning applications. In at least one embodiment, PPU 3000 isconfigured to accelerate deep learning systems and applicationsincluding following non-limiting examples: autonomous vehicle platforms,deep learning, high-accuracy speech, image, text recognition systems,intelligent video analytics, molecular simulations, drug discovery,disease diagnosis, weather forecasting, big data analytics, astronomy,molecular dynamics simulation, financial modeling, robotics, factoryautomation, real-time language translation, online search optimizations,and personalized user recommendations, and more.

In at least one embodiment, PPU 3000 includes, without limitation, anInput/Output (“I/O”) unit 3006, a front-end unit 3010, a scheduler(sequencer) unit 3012, a work distribution unit 3014, a hub 3016, acrossbar (“XBar”) 3020, one or more general processing clusters (“GPCs”)3018, and one or more partition units (“memory partition units”) 3022.In at least one embodiment, PPU 3000 is connected to a host processor orother PPUs 3000 via one or more high-speed GPU interconnects (“GPUinterconnects”) 3008. In at least one embodiment, PPU 3000 is connectedto a host processor or other peripheral devices via a system bus 3002.In at least one embodiment, PPU 3000 is connected to a local memorycomprising one or more memory devices (“memory”) 3004. In at least oneembodiment, memory devices 3004 include, without limitation, one or moredynamic random access memory (“DRAM”) devices. In at least oneembodiment, one or more DRAM devices are configured and/or configurableas high-bandwidth memory (“HBM”) subsystems, with multiple DRAM diesstacked within each device.

In at least one embodiment, high-speed GPU interconnect 3008 may referto a wire-based multi-lane communications link that is used by systemsto scale and include one or more PPUs 3000 combined with one or morecentral processing units (“CPUs”), supports cache coherence between PPUs3000 and CPUs, and CPU mastering. In at least one embodiment, dataand/or commands are transmitted by high-speed GPU interconnect 3008through hub 3016 to/from other units of PPU 3000 such as one or morecopy engines, video encoders, video decoders, power management units,and other components which may not be explicitly illustrated in FIG. 30.

In at least one embodiment, I/O unit 3006 is configured to transmit andreceive communications (e.g., commands, data) from a host processor (notillustrated in FIG. 30 ) over system bus 3002. In at least oneembodiment, I/O unit 3006 communicates with host processor directly viasystem bus 3002 or through one or more intermediate devices such as amemory bridge. In at least one embodiment, I/O unit 3006 may communicatewith one or more other processors, such as one or more of PPUs 3000 viasystem bus 3002. In at least one embodiment, I/O unit 3006 implements aPeripheral Component Interconnect Express (“PCIe”) interface forcommunications over a PCIe bus. In at least one embodiment, I/O unit3006 implements interfaces for communicating with external devices.

In at least one embodiment, I/O unit 3006 decodes packets received viasystem bus 3002. In at least one embodiment, at least some packetsrepresent commands configured to cause PPU 3000 to perform variousoperations. In at least one embodiment, I/O unit 3006 transmits decodedcommands to various other units of PPU 3000 as specified by commands. Inat least one embodiment, commands are transmitted to front-end unit 3010and/or transmitted to hub 3016 or other units of PPU 3000 such as one ormore copy engines, a video encoder, a video decoder, a power managementunit, etc. (not explicitly illustrated in FIG. 30 ). In at least oneembodiment, I/O unit 3006 is configured to route communications betweenand among various logical units of PPU 3000.

In at least one embodiment, a program executed by host processor encodesa command stream in a buffer that provides workloads to PPU 3000 forprocessing. In at least one embodiment, a workload comprisesinstructions and data to be processed by those instructions. In at leastone embodiment, a buffer is a region in a memory that is accessible(e.g., read/write) by both a host processor and PPU 3000— a hostinterface unit may be configured to access that buffer in a systemmemory connected to system bus 3002 via memory requests transmitted oversystem bus 3002 by I/O unit 3006. In at least one embodiment, a hostprocessor writes a command stream to a buffer and then transmits apointer to a start of a command stream to PPU 3000 such that front-endunit 3010 receives pointers to one or more command streams and managesone or more command streams, reading commands from command streams andforwarding commands to various units of PPU 3000.

In at least one embodiment, front-end unit 3010 is coupled to schedulerunit 3012 (which may be referred to as a sequencer unit, a threadsequencer, and/or an asynchronous compute engine) that conFIGS. variousGPCs 3018 to process tasks defined by one or more command streams. In atleast one embodiment, scheduler unit 3012 is configured to track stateinformation related to various tasks managed by scheduler unit 3012where state information may indicate which of GPCs 3018 a task isassigned to, whether task is active or inactive, a priority levelassociated with task, and so forth. In at least one embodiment,scheduler unit 3012 manages execution of a plurality of tasks on one ormore of GPCs 3018.

In at least one embodiment, scheduler unit 3012 is coupled to workdistribution unit 3014 that is configured to dispatch tasks forexecution on GPCs 3018. In at least one embodiment, work distributionunit 3014 tracks a number of scheduled tasks received from schedulerunit 3012 and work distribution unit 3014 manages a pending task pooland an active task pool for each of GPCs 3018. In at least oneembodiment, pending task pool comprises a number of slots (e.g., 32slots) that contain tasks assigned to be processed by a particular GPC3018; an active task pool may comprise a number of slots (e.g., 4 slots)for tasks that are actively being processed by GPCs 3018 such that asone of GPCs 3018 completes execution of a task, that task is evictedfrom that active task pool for GPC 3018 and another task from a pendingtask pool is selected and scheduled for execution on GPC 3018. In atleast one embodiment, if an active task is idle on GPC 3018, such aswhile waiting for a data dependency to be resolved, then that activetask is evicted from GPC 3018 and returned to that pending task poolwhile another task in that pending task pool is selected and scheduledfor execution on GPC 3018.

In at least one embodiment, work distribution unit 3014 communicateswith one or more GPCs 3018 via XBar 3020. In at least one embodiment,XBar 3020 is an interconnect network that couples many of units of PPU3000 to other units of PPU 3000 and can be configured to couple workdistribution unit 3014 to a particular GPC 3018. In at least oneembodiment, one or more other units of PPU 3000 may also be connected toXBar 3020 via hub 3016.

In at least one embodiment, tasks are managed by scheduler unit 3012 anddispatched to one of GPCs 3018 by work distribution unit 3014. In atleast one embodiment, GPC 3018 is configured to process task andgenerate results. In at least one embodiment, results may be consumed byother tasks within GPC 3018, routed to a different GPC 3018 via XBar3020, or stored in memory 3004. In at least one embodiment, results canbe written to memory 3004 via partition units 3022, which implement amemory interface for reading and writing data to/from memory 3004. In atleast one embodiment, results can be transmitted to another PPU or CPUvia high-speed GPU interconnect 3008. In at least one embodiment, PPU3000 includes, without limitation, a number U of partition units 3022that is equal to a number of separate and distinct memory devices 3004coupled to PPU 3000, as described in more detail herein in conjunctionwith FIG. 32 .

In at least one embodiment, a host processor executes a driver kernelthat implements an application programming interface (“API”) thatenables one or more applications executing on a host processor toschedule operations for execution on PPU 3000. In at least oneembodiment, multiple compute applications are simultaneously executed byPPU 3000 and PPU 3000 provides isolation, quality of service (“QoS”),and independent address spaces for multiple compute applications. In atleast one embodiment, an application generates instructions (e.g., inform of API calls) that cause a driver kernel to generate one or moretasks for execution by PPU 3000 and that driver kernel outputs tasks toone or more streams being processed by PPU 3000. In at least oneembodiment, each task comprises one or more groups of related threads,which may be referred to as a warp, wavefront, and/or wave. In at leastone embodiment, a warp, wavefront, and/or wave comprises a plurality ofrelated threads (e.g., 32 threads) that can be executed in parallel. Inat least one embodiment, cooperating threads can refer to a plurality ofthreads including instructions to perform task and that exchange datathrough shared memory. In at least one embodiment, threads andcooperating threads are described in more detail in conjunction withFIG. 32 .

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, deep learning application processor is used to train amachine learning model, such as a neural network, to predict or inferinformation provided to PPU 3000. In at least one embodiment, deeplearning application processor is used to infer or predict informationbased on a trained machine learning model (e.g., neural network) thathas been trained by another processor or system or by PPU 3000. In atleast one embodiment, PPU 3000 may be used to perform one or more neuralnetwork use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 30 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 31 illustrates a general processing cluster (“GPC”) 3100, accordingto at least one embodiment. In at least one embodiment, GPC 3100 is GPC3018 of FIG. 30 . In at least one embodiment, each GPC 3100 includes,without limitation, a number of hardware units for processing tasks andeach GPC 3100 includes, without limitation, a pipeline manager 3102, apre-raster operations unit (“preROP”) 3104, a raster engine 3108, a workdistribution crossbar (“WDX”) 3116, a memory management unit (“MMU”)3118, one or more Data Processing Clusters (“DPCs”) 3106, and anysuitable combination of parts.

In at least one embodiment, operation of GPC 3100 is controlled bypipeline manager 3102. In at least one embodiment, pipeline manager 3102manages configuration of one or more DPCs 3106 for processing tasksallocated to GPC 3100. In at least one embodiment, pipeline manager 3102conFIGS. at least one of one or more DPCs 3106 to implement at least aportion of a graphics rendering pipeline. In at least one embodiment,DPC 3106 is configured to execute a vertex shader program on aprogrammable streaming multi-processor (“SM”) 3114. In at least oneembodiment, pipeline manager 3102 is configured to route packetsreceived from a work distribution unit to appropriate logical unitswithin GPC 3100, in at least one embodiment, and some packets may berouted to fixed function hardware units in preROP 3104 and/or rasterengine 3108 while other packets may be routed to DPCs 3106 forprocessing by a primitive engine 3112 or SM 3114. In at least oneembodiment, pipeline manager 3102 conFIGS. at least one of DPCs 3106 toimplement a neural network model and/or a computing pipeline.

In at least one embodiment, preROP unit 3104 is configured, in at leastone embodiment, to route data generated by raster engine 3108 and DPCs3106 to a Raster Operations (“ROP”) unit in partition unit 3022,described in more detail above in conjunction with FIG. 30 . In at leastone embodiment, preROP unit 3104 is configured to perform optimizationsfor color blending, organize pixel data, perform address translations,and more. In at least one embodiment, raster engine 3108 includes,without limitation, a number of fixed function hardware units configuredto perform various raster operations, in at least one embodiment, andraster engine 3108 includes, without limitation, a setup engine, acoarse raster engine, a culling engine, a clipping engine, a fine rasterengine, a tile coalescing engine, and any suitable combination thereof.In at least one embodiment, setup engine receives transformed verticesand generates plane equations associated with geometric primitivedefined by vertices; plane equations are transmitted to a coarse rasterengine to generate coverage information (e.g., an x, y coverage mask fora tile) for primitive; output of a coarse raster engine is transmittedto a culling engine where fragments associated with a primitive thatfail a z-test are culled, and transmitted to a clipping engine wherefragments lying outside a viewing frustum are clipped. In at least oneembodiment, fragments that survive clipping and culling are passed to afine raster engine to generate attributes for pixel fragments based onplane equations generated by a setup engine. In at least one embodiment,an output of raster engine 3108 comprises fragments to be processed byany suitable entity, such as by a fragment shader implemented within DPC3106.

In at least one embodiment, each DPC 3106 included in GPC 3100comprises, without limitation, an M-Pipe Controller (“MPC”) 3110;primitive engine 3112; one or more SMs 3114; and any suitablecombination thereof. In at least one embodiment, MPC 3110 controlsoperation of DPC 3106, routing packets received from pipeline manager3102 to appropriate units in DPC 3106. In at least one embodiment,packets associated with a vertex are routed to primitive engine 3112,which is configured to fetch vertex attributes associated with a vertexfrom memory; in contrast, packets associated with a shader program maybe transmitted to SM 3114.

In at least one embodiment, SM 3114 comprises, without limitation, aprogrammable streaming processor that is configured to process tasksrepresented by a number of threads. In at least one embodiment, SM 3114is multi-threaded and configured to execute a plurality of threads(e.g., 32 threads) from a particular group of threads concurrently andimplements a Single-Instruction, Multiple-Data (“SIMD”) architecturewhere each thread in a group of threads (e.g., a warp, wavefront, wave)is configured to process a different set of data based on same set ofinstructions. In at least one embodiment, all threads in group ofthreads execute a common set of instructions. In at least oneembodiment, SM 3114 implements a Single-Instruction, Multiple Thread(“SIMT”) architecture wherein each thread in a group of threads isconfigured to process a different set of data based on that common setof instructions, but where individual threads in a group of threads areallowed to diverge during execution. In at least one embodiment, aprogram counter, call stack, and execution state is maintained for eachwarp (which may be referred to as wavefronts and/or waves), enablingconcurrency between warps and serial execution within warps when threadswithin a warp diverge. In another embodiment, a program counter, callstack, and execution state is maintained for each individual thread,enabling equal concurrency between all threads, within and betweenwarps. In at least one embodiment, execution state is maintained foreach individual thread and threads executing common instructions may beconverged and executed in parallel for better efficiency. At least oneembodiment of SM 3114 is described in more detail herein.

In at least one embodiment, MMU 3118 provides an interface between GPC3100 and a memory partition unit (e.g., partition unit 3022 of FIG. 30 )and MMU 3118 provides translation of virtual addresses into physicaladdresses, memory protection, and arbitration of memory requests. In atleast one embodiment, MMU 3118 provides one or more translationlookaside buffers (“TLBs”) for performing translation of virtualaddresses into physical addresses in memory.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, deep learning application processor is used to train amachine learning model, such as a neural network, to predict or inferinformation provided to GPC 3100. In at least one embodiment, GPC 3100is used to infer or predict information based on a trained machinelearning model (e.g., neural network) that has been trained by anotherprocessor or system or by GPC 3100. In at least one embodiment, GPC 3100may be used to perform one or more neural network use cases describedherein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 31 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 32 illustrates a memory partition unit 3200 of a parallelprocessing unit (“PPU”), in accordance with at least one embodiment. Inat least one embodiment, memory partition unit 3200 includes, withoutlimitation, a Raster Operations (“ROP”) unit 3202, a level two (“L2”)cache 3204, a memory interface 3206, and any suitable combinationthereof. In at least one embodiment, memory interface 3206 is coupled tomemory. In at least one embodiment, memory interface 3206 may implement32, 64, 128, 1024-bit data buses, or like, for high-speed data transfer.In at least one embodiment, PPU incorporates U memory interfaces 3206where U is a positive integer, with one memory interface 3206 per pairof partition units 3200, where each pair of partition units 3200 isconnected to a corresponding memory device. For example, in at least oneembodiment, PPU may be connected to up to Y memory devices, such as highbandwidth memory stacks or graphics double-data-rate, version 5,synchronous dynamic random access memory (“GDDR5 SDRAM”).

In at least one embodiment, memory interface 3206 implements a highbandwidth memory second generation (“HBM2”) memory interface and Yequals half of U. In at least one embodiment, HBM2 memory stacks arelocated on a physical package with a PPU, providing substantial powerand area savings compared with conventional GDDR5 SDRAM systems. In atleast one embodiment, each HBM2 stack includes, without limitation, fourmemory dies with Y=4, with each HBM2 stack including two 128-bitchannels per die for a total of 8 channels and a data bus width of 1024bits. In at least one embodiment, that memory supports Single-ErrorCorrecting Double-Error Detecting (“SECDED”) Error Correction Code(“ECC”) to protect data. In at least one embodiment, ECC can providehigher reliability for compute applications that are sensitive to datacorruption.

In at least one embodiment, PPU implements a multi-level memoryhierarchy. In at least one embodiment, memory partition unit 3200supports a unified memory to provide a single unified virtual addressspace for central processing unit (“CPU”) and PPU memory, enabling datasharing between virtual memory systems. In at least one embodimentfrequency of accesses by a PPU to a memory located on other processorsis traced to ensure that memory pages are moved to physical memory ofPPU that is accessing pages more frequently. In at least one embodiment,high-speed GPU interconnect 3008 supports address translation servicesallowing PPU to directly access a CPU's page tables and providing fullaccess to CPU memory by a PPU.

In at least one embodiment, copy engines transfer data between multiplePPUs or between PPUs and CPUs. In at least one embodiment, copy enginescan generate page faults for addresses that are not mapped into pagetables and memory partition unit 3200 then services page faults, mappingaddresses into page table, after which copy engine performs a transfer.In at least one embodiment, memory is pinned (i.e., non-pageable) formultiple copy engine operations between multiple processors,substantially reducing available memory. In at least one embodiment,with hardware page faulting, addresses can be passed to copy engineswithout regard as to whether memory pages are resident, and a copyprocess is transparent.

Data from memory 3004 of FIG. 30 or other system memory is fetched bymemory partition unit 3200 and stored in L2 cache 3204, which is locatedon-chip and is shared between various GPCs, in accordance with at leastone embodiment. Each memory partition unit 3200, in at least oneembodiment, includes, without limitation, at least a portion of L2 cacheassociated with a corresponding memory device. In at least oneembodiment, lower level caches are implemented in various units withinGPCs. In at least one embodiment, each of SMs 3114 in FIG. 31 mayimplement a Level 1 (“L1”) cache wherein that L1 cache is private memorythat is dedicated to a particular SM 3114 and data from L2 cache 3204 isfetched and stored in each L1 cache for processing in functional unitsof SMs 3114. In at least one embodiment, L2 cache 3204 is coupled tomemory interface 3206 and XBar 3020 shown in FIG. 30 .

ROP unit 3202 performs graphics raster operations related to pixelcolor, such as color compression, pixel blending, and more, in at leastone embodiment. ROP unit 3202, in at least one embodiment, implementsdepth testing in conjunction with raster engine 3108, receiving a depthfor a sample location associated with a pixel fragment from a cullingengine of raster engine 3108. In at least one embodiment, depth istested against a corresponding depth in a depth buffer for a samplelocation associated with a fragment. In at least one embodiment, if thatfragment passes that depth test for that sample location, then ROP unit3202 updates depth buffer and transmits a result of that depth test toraster engine 3108. It will be appreciated that a number of partitionunits 3200 may be different than a number of GPCs and, therefore, eachROP unit 3202 can, in at least one embodiment, be coupled to each GPC.In at least one embodiment, ROP unit 3202 tracks packets received fromdifferent GPCs and determines whether a result generated by ROP unit3202 is to be routed to through XBar 3020.

FIG. 33 illustrates a streaming multi-processor (“SM”) 3300, accordingto at least one embodiment. In at least one embodiment, SM 3300 is SM ofFIG. 31 . In at least one embodiment, SM 3300 includes, withoutlimitation, an instruction cache 3302, one or more scheduler units 3304(which may be referred to as sequencer units), a register file 3308, oneor more processing cores (“cores”) 3310, one or more special functionunits (“SFUs”) 3312, one or more load/store units (“LSUs”) 3314, aninterconnect network 3316, a shared memory/level one (“L1”) cache 3318,and/or any suitable combination thereof. In at least one embodiment,LSUs 3314 perform load of store operations corresponding toloading/storing data (e.g., instructions) to perform an operation (e.g.,perform an API, an API call).

In at least one embodiment, a work distribution unit dispatches tasksfor execution on general processing clusters (“GPCs”) of parallelprocessing units (“PPUs”) and each task is allocated to a particularData Processing Cluster (“DPC”) within a GPC and, if a task isassociated with a shader program, that task is allocated to one of SMs3300 (which may be referred to as CUs and/or slices). In at least oneembodiment, scheduler unit 3304 (which may be referred to as a sequencerand/or asynchronous compute engine) receives tasks from a workdistribution unit and manages instruction scheduling for one or morethread blocks assigned to SM 3300. In at least one embodiment, schedulerunit 3304 schedules thread blocks for execution as warps (which may bereferred to as wavefronts and/or waves) of parallel threads, whereineach thread block is allocated at least one warp. In at least oneembodiment, each warp executes threads. In at least one embodiment,scheduler unit 3304 manages a plurality of different thread blocks,allocating warps to different thread blocks and then dispatchinginstructions from plurality of different cooperative groups to variousfunctional units (e.g., processing cores 3310, SFUs 3312, and LSUs 3314)during each clock cycle.

In at least one embodiment, Cooperative Groups (which may also bereferred to as wavefronts and/or waves) may refer to a programming modelfor organizing groups of communicating threads that allows developers toexpress granularity at which threads are communicating, enablingexpression of richer, more efficient parallel decompositions. In atleast one embodiment, cooperative launch APIs support synchronizationamongst thread blocks for execution of parallel algorithms. In at leastone embodiment, applications of conventional programming models providea single, simple construct for synchronizing cooperating threads: abarrier across all threads of a thread block (e.g., syncthreads( )function). However, in at least one embodiment, programmers may definegroups of threads at smaller than thread block granularities andsynchronize within defined groups to enable greater performance, designflexibility, and software reuse in form of collective group-widefunction interfaces. In at least one embodiment, Cooperative Groupsenables programmers to define groups of threads explicitly at sub-block(i.e., as small as a single thread) and multi-block granularities, andto perform collective operations such as synchronization on threads in acooperative group. In at least one embodiment, that programming modelsupports clean composition across software boundaries, so that librariesand utility functions can synchronize safely within their local contextwithout having to make assumptions about convergence. In at least oneembodiment, Cooperative Groups primitives enable new patterns ofcooperative parallelism, including, without limitation,producer-consumer parallelism, opportunistic parallelism, and globalsynchronization across an entire grid of thread blocks.

In at least one embodiment, a dispatch unit 3306 is configured totransmit instructions to one or more functional units and scheduler unit3304 and includes, without limitation, two dispatch units 3306 thatenable two different instructions from a common warp to be dispatchedduring each clock cycle. In at least one embodiment, each scheduler unit3304 includes a single dispatch unit 3306 or additional dispatch units3306.

In at least one embodiment, each SM 3300 (which may be referred to as aCU and/or slice), in at least one embodiment, includes, withoutlimitation, register file 3308 that provides a set of registers forfunctional units of SM 3300. In at least one embodiment, register file3308 is divided between each functional unit such that each functionalunit is allocated a dedicated portion of register file 3308. In at leastone embodiment, register file 3308 is divided between different warpsbeing executed by SM 3300 and register file 3308 provides temporarystorage for operands connected to data paths of functional units. In atleast one embodiment, each SM 3300 comprises, without limitation, aplurality of L processing cores 3310, where L is a positive integer. Inat least one embodiment, SM 3300 includes, without limitation, a largenumber (e.g., 128 or more) of distinct processing cores 3310. In atleast one embodiment, each processing core 3310 includes, withoutlimitation, a fully-pipelined, single-precision, double-precision,and/or mixed precision processing unit that includes, withoutlimitation, a floating point arithmetic logic unit and an integerarithmetic logic unit. In at least one embodiment, floating pointarithmetic logic units implement IEEE 754-2008 standard for floatingpoint arithmetic. In at least one embodiment, processing cores 3310include, without limitation, 64 single-precision (32-bit) floating pointcores, 64 integer cores, 32 double-precision (64-bit) floating pointcores, and 8 tensor cores.

Tensor cores are configured to perform matrix operations in accordancewith at least one embodiment. In at least one embodiment, one or moretensor cores are included in processing cores 3310. In at least oneembodiment, tensor cores are configured to perform deep learning matrixarithmetic, such as convolution operations for neural network trainingand inferencing. In at least one embodiment, each tensor core operateson a 4×4 matrix and performs a matrix multiply and accumulate operation,D=A×B+C, where A, B, C, and D are 4×4 matrices.

In at least one embodiment, matrix multiply inputs A and B are 16-bitfloating point matrices and accumulation matrices C and D are 16-bitfloating point or 32-bit floating point matrices. In at least oneembodiment, tensor cores operate on 16-bit floating point input datawith 32-bit floating point accumulation. In at least one embodiment,16-bit floating point multiply uses 64 operations and results in a fullprecision product that is then accumulated using 32-bit floating pointaddition with other intermediate products for a 4×4×4 matrix multiply.Tensor cores are used to perform much larger two-dimensional or higherdimensional matrix operations, built up from these smaller elements, inat least one embodiment. In at least one embodiment, an API, such as aCUDA 9 C++ API, exposes specialized matrix load, matrix multiply andaccumulate, and matrix store operations to efficiently use tensor coresfrom a CUDA-C++ program. In at least one embodiment, at a CUDA level, awarp-level interface assumes 16×16 size matrices spanning all 32 threadsof warp (which may be referred to as a wavefront and/or wave).

In at least one embodiment, each SM 3300 comprises, without limitation,M SFUs 3312 that perform special functions (e.g., attribute evaluation,reciprocal square root, and like). In at least one embodiment, SFUs 3312include, without limitation, a tree traversal unit configured totraverse a hierarchical tree data structure. In at least one embodiment,SFUs 3312 include, without limitation, a texture unit configured toperform texture map filtering operations. In at least one embodiment,texture units are configured to load texture maps (e.g., a 2D array oftexels) from memory and sample texture maps to produce sampled texturevalues for use in shader programs executed by SM 3300. In at least oneembodiment, texture maps are stored in shared memory/L1 cache 3318. Inat least one embodiment, texture units implement texture operations suchas filtering operations using mip-maps (e.g., texture maps of varyinglevels of detail), in accordance with at least one embodiment. In atleast one embodiment, each SM 3300 includes, without limitation, twotexture units.

Each SM 3300 comprises, without limitation, N LSUs 3314 that implementload and store operations between shared memory/L1 cache 3318 andregister file 3308, in at least one embodiment. Interconnect network3316 connects each functional unit to register file 3308 and LSU 3314 toregister file 3308 and shared memory/L1 cache 3318 in at least oneembodiment. In at least one embodiment, interconnect network 3316 is acrossbar that can be configured to connect any functional units to anyregisters in register file 3308 and connect LSUs 3314 to register file3308 and memory locations in shared memory/L1 cache 3318.

In at least one embodiment, shared memory/L1 cache 3318 is an array ofon-chip memory that allows for data storage and communication between SM3300 and primitive engine and between threads in SM 3300, in at leastone embodiment. In at least one embodiment, shared memory/L1 cache 3318comprises, without limitation, 128 KB of storage capacity and is in apath from SM 3300 to a partition unit. In at least one embodiment,shared memory/L1 cache 3318, in at least one embodiment, is used tocache reads and writes. In at least one embodiment, one or more ofshared memory/L1 cache 3318, L2 cache, and memory are backing stores.

Combining data cache and shared memory functionality into a singlememory block provides improved performance for both types of memoryaccesses, in at least one embodiment. In at least one embodiment,capacity is used or is usable as a cache by programs that do not useshared memory, such as if shared memory is configured to use half of acapacity, and texture and load/store operations can use remainingcapacity. Integration within shared memory/L1 cache 3318 enables sharedmemory/L1 cache 3318 to function as a high-throughput conduit forstreaming data while simultaneously providing high-bandwidth andlow-latency access to frequently reused data, in accordance with atleast one embodiment. In at least one embodiment, when configured forgeneral purpose parallel computation, a simpler configuration can beused compared with graphics processing. In at least one embodiment,fixed function graphics processing units are bypassed, creating a muchsimpler programming model. In a general purpose parallel computationconfiguration, a work distribution unit assigns and distributes blocksof threads directly to DPCs, in at least one embodiment. In at least oneembodiment, threads in a block execute a common program, using a uniquethread ID in calculation to ensure each thread generates unique results,using SM 3300 to execute program and perform calculations, sharedmemory/L1 cache 3318 to communicate between threads, and LSU 3314 toread and write global memory through shared memory/L1 cache 3318 andmemory partition unit. In at least one embodiment, when configured forgeneral purpose parallel computation, SM 3300 writes commands thatscheduler unit 3304 can use to launch new work on DPCs.

In at least one embodiment, a PPU is included in or coupled to a desktopcomputer, a laptop computer, a tablet computer, servers, supercomputers,a smart-phone (e.g., a wireless, hand-held device), personal digitalassistant (“PDA”), a digital camera, a vehicle, a head mounted display,a hand-held electronic device, and more. In at least one embodiment, aPPU is embodied on a single semiconductor substrate. In at least oneembodiment, a PPU is included in a system-on-a-chip (“SoC”) along withone or more other devices such as additional PPUs, memory, a reducedinstruction set computer (“RISC”) CPU, a memory management unit (“MMU”),a digital-to-analog converter (“DAC”), and like.

In at least one embodiment, a PPU may be included on a graphics cardthat includes one or more memory devices. In at least one embodiment,that graphics card may be configured to interface with a PCIe slot on amotherboard of a desktop computer. In at least one embodiment, that PPUmay be an integrated graphics processing unit (“iGPU”) included inchipset of a motherboard.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B. In at least oneembodiment, deep learning application processor is used to train amachine learning model, such as a neural network, to predict or inferinformation provided to SM 3300. In at least one embodiment, SM 3300 isused to infer or predict information based on a trained machine learningmodel (e.g., neural network) that has been trained by another processoror system or by SM 3300. In at least one embodiment, SM 3300 may be usedto perform one or more neural network use cases described herein.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 33 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

Embodiments are disclosed related a virtualized computing platform foradvanced computing, such as image inferencing and image processing inmedical applications. Without limitation, embodiments may includeradiography, magnetic resonance imaging (MRI), nuclear medicine,ultrasound, sonography, elastography, photoacoustic imaging, tomography,echocardiography, functional near-infrared spectroscopy, and magneticparticle imaging, or a combination thereof. In at least one embodiment,a virtualized computing platform and associated processes describedherein may additionally or alternatively be used, without limitation, inforensic science analysis, sub-surface detection and imaging (e.g., oilexploration, archaeology, paleontology, etc.), topography, oceanography,geology, osteology, meteorology, intelligent area or object tracking andmonitoring, sensor data processing (e.g., RADAR, SONAR, LIDAR, etc.),and/or genomics and gene sequencing.

With reference to FIG. 34 , FIG. 34 is an example data flow diagram fora process 3400 of generating and deploying an image processing andinferencing pipeline, in accordance with at least one embodiment. In atleast one embodiment, process 3400 may be deployed for use with imagingdevices, processing devices, genomics devices, gene sequencing devices,radiology devices, and/or other device types at one or more facilities3402, such as medical facilities, hospitals, healthcare institutes,clinics, research or diagnostic labs, etc. In at least one embodiment,process 3400 may be deployed to perform genomics analysis andinferencing on sequencing data. Examples of genomic analyses that may beperformed using systems and processes described herein include, withoutlimitation, variant calling, mutation detection, and gene expressionquantification.

In at least one embodiment, process 3400 may be executed within atraining system 3404 and/or a deployment system 3406. In at least oneembodiment, training system 3404 may be used to perform training,deployment, and implementation of machine learning models (e.g., neuralnetworks, object detection algorithms, computer vision algorithms, etc.)for use in deployment system 3406. In at least one embodiment,deployment system 3406 may be configured to offload processing andcompute resources among a distributed computing environment to reduceinfrastructure requirements at facility 3402. In at least oneembodiment, deployment system 3406 may provide a streamlined platformfor selecting, customizing, and implementing virtual instruments for usewith imaging devices (e.g., Mill, CT Scan, X-Ray, Ultrasound, etc.) orsequencing devices at facility 3402. In at least one embodiment, virtualinstruments may include software-defined applications for performing oneor more processing operations with respect to imaging data generated byimaging devices, sequencing devices, radiology devices, and/or otherdevice types. In at least one embodiment, one or more applications in apipeline may use or call upon services (e.g., inference, visualization,compute, AI, etc.) of deployment system 3406 during execution ofapplications.

In at least one embodiment, some of applications used in advancedprocessing and inferencing pipelines may use machine learning models orother AI to perform one or more processing steps. In at least oneembodiment, machine learning models may be trained at facility 3402using data 3408 (such as imaging data) generated at facility 3402 (andstored on one or more picture archiving and communication system (PACS)servers at facility 3402), may be trained using imaging or sequencingdata 3408 from another facility or facilities (e.g., a differenthospital, lab, clinic, etc.), or a combination thereof. In at least oneembodiment, training system 3404 may be used to provide applications,services, and/or other resources for generating working, deployablemachine learning models for deployment system 3406.

In at least one embodiment, a model registry 3424 may be backed byobject storage that may support versioning and object metadata. In atleast one embodiment, object storage may be accessible through, forexample, a cloud storage (e.g., a cloud 3526 of FIG. 35 ) compatibleapplication programming interface (API) from within a cloud platform. Inat least one embodiment, machine learning models within model registry3424 may uploaded, listed, modified, or deleted by developers orpartners of a system interacting with an API. In at least oneembodiment, an API may provide access to methods that allow users withappropriate credentials to associate models with applications, such thatmodels may be executed as part of execution of containerizedinstantiations of applications.

In at least one embodiment, a training pipeline 3504 (FIG. 35 ) mayinclude a scenario where facility 3402 is training their own machinelearning model, or has an existing machine learning model that needs tobe optimized or updated. In at least one embodiment, imaging data 3408generated by imaging device(s), sequencing devices, and/or other devicetypes may be received. In at least one embodiment, once imaging data3408 is received, AI-assisted annotation 3410 may be used to aid ingenerating annotations corresponding to imaging data 3408 to be used asground truth data for a machine learning model. In at least oneembodiment, AI-assisted annotation 3410 may include one or more machinelearning models (e.g., convolutional neural networks (CNNs)) that may betrained to generate annotations corresponding to certain types ofimaging data 3408 (e.g., from certain devices) and/or certain types ofanomalies in imaging data 3408. In at least one embodiment, AI-assistedannotations 3410 may then be used directly, or may be adjusted orfine-tuned using an annotation tool (e.g., by a researcher, a clinician,a doctor, a scientist, etc.), to generate ground truth data. In at leastone embodiment, in some examples, labeled clinic data 3412 (e.g.,annotations provided by a clinician, doctor, scientist, technician,etc.) may be used as ground truth data for training a machine learningmodel. In at least one embodiment, AI-assisted annotations 3410, labeledclinic data 3412, or a combination thereof may be used as ground truthdata for training a machine learning model. In at least one embodiment,a trained machine learning model may be referred to as an output model3416, and may be used by deployment system 3406, as described herein.

In at least one embodiment, training pipeline 3504 (FIG. 35 ) mayinclude a scenario where facility 3402 needs a machine learning modelfor use in performing one or more processing tasks for one or moreapplications in deployment system 3406, but facility 3402 may notcurrently have such a machine learning model (or may not have a modelthat is optimized, efficient, or effective for such purposes). In atleast one embodiment, an existing machine learning model may be selectedfrom model registry 3424. In at least one embodiment, model registry3424 may include machine learning models trained to perform a variety ofdifferent inference tasks on imaging data. In at least one embodiment,machine learning models in model registry 3424 may have been trained onimaging data from different facilities than facility 3402 (e.g.,facilities remotely located). In at least one embodiment, machinelearning models may have been trained on imaging data from one location,two locations, or any number of locations. In at least one embodiment,when being trained on imaging data from a specific location, trainingmay take place at that location, or at least in a manner that protectsconfidentiality of imaging data or restricts imaging data from beingtransferred off-premises (e.g., to comply with HIPAA regulations,privacy regulations, etc.). In at least one embodiment, once a model istrained—or partially trained—at one location, a machine learning modelmay be added to model registry 3424. In at least one embodiment, amachine learning model may then be retrained, or updated, at any numberof other facilities, and a retrained or updated model may be madeavailable in model registry 3424. In at least one embodiment, a machinelearning model may then be selected from model registry 3424— andreferred to as output model 3416— and may be used in deployment system3406 to perform one or more processing tasks for one or moreapplications of a deployment system.

In at least one embodiment, training pipeline 3504 (FIG. 35 ) may beused in a scenario that includes facility 3402 requiring a machinelearning model for use in performing one or more processing tasks forone or more applications in deployment system 3406, but facility 3402may not currently have such a machine learning model (or may not have amodel that is optimized, efficient, or effective for such purposes). Inat least one embodiment, a machine learning model selected from modelregistry 3424 might not be fine-tuned or optimized for imaging data 3408generated at facility 3402 because of differences in populations,genetic variations, robustness of training data used to train a machinelearning model, diversity in anomalies of training data, and/or otherissues with training data. In at least one embodiment, AI-assistedannotation 3410 may be used to aid in generating annotationscorresponding to imaging data 3408 to be used as ground truth data forretraining or updating a machine learning model. In at least oneembodiment, labeled clinic data 3412 (e.g., annotations provided by aclinician, doctor, scientist, etc.) may be used as ground truth data fortraining a machine learning model. In at least one embodiment,retraining or updating a machine learning model may be referred to asmodel training 3414. In at least one embodiment, model training3414—e.g., AI-assisted annotations 3410, labeled clinic data 3412, or acombination thereof—may be used as ground truth data for retraining orupdating a machine learning model.

In at least one embodiment, deployment system 3406 may include software3418, services 3420, hardware 3422, and/or other components, features,and functionality. In at least one embodiment, deployment system 3406may include a software “stack,” such that software 3418 may be built ontop of services 3420 and may use services 3420 to perform some or all ofprocessing tasks, and services 3420 and software 3418 may be built ontop of hardware 3422 and use hardware 3422 to execute processing,storage, and/or other compute tasks of deployment system 3406.

In at least one embodiment, software 3418 may include any number ofdifferent containers, where each container may execute an instantiationof an application. In at least one embodiment, each application mayperform one or more processing tasks in an advanced processing andinferencing pipeline (e.g., inferencing, object detection, featuredetection, segmentation, image enhancement, calibration, etc.). In atleast one embodiment, for each type of imaging device (e.g., CT, MM,X-Ray, ultrasound, sonography, echocardiography, etc.), sequencingdevice, radiology device, genomics device, etc., there may be any numberof containers that may perform a data processing task with respect toimaging data 3408 (or other data types, such as those described herein)generated by a device. In at least one embodiment, an advancedprocessing and inferencing pipeline may be defined based on selectionsof different containers that are desired or required for processingimaging data 3408, in addition to containers that receive and configureimaging data for use by each container and/or for use by facility 3402after processing through a pipeline (e.g., to convert outputs back to ausable data type, such as digital imaging and communications in medicine(DICOM) data, radiology information system (RIS) data, clinicalinformation system (CIS) data, remote procedure call (RPC) data, datasubstantially compliant with a representation state transfer (REST)interface, data substantially compliant with a file-based interface,and/or raw data, for storage and display at facility 3402). In at leastone embodiment, a combination of containers within software 3418 (e.g.,that make up a pipeline) may be referred to as a virtual instrument (asdescribed in more detail herein), and a virtual instrument may leverageservices 3420 and hardware 3422 to execute some or all processing tasksof applications instantiated in containers.

In at least one embodiment, a data processing pipeline may receive inputdata (e.g., imaging data 3408) in a DICOM, RIS, CIS, REST compliant,RPC, raw, and/or other format in response to an inference request (e.g.,a request from a user of deployment system 3406, such as a clinician, adoctor, a radiologist, etc.). In at least one embodiment, input data maybe representative of one or more images, video, and/or other datarepresentations generated by one or more imaging devices, sequencingdevices, radiology devices, genomics devices, and/or other device types.In at least one embodiment, data may undergo pre-processing as part ofdata processing pipeline to prepare data for processing by one or moreapplications. In at least one embodiment, post-processing may beperformed on an output of one or more inferencing tasks or otherprocessing tasks of a pipeline to prepare an output data for a nextapplication and/or to prepare output data for transmission and/or use bya user (e.g., as a response to an inference request). In at least oneembodiment, inferencing tasks may be performed by one or more machinelearning models, such as trained or deployed neural networks, which mayinclude output models 3416 of training system 3404.

In at least one embodiment, tasks of data processing pipeline may beencapsulated in a container(s) that each represent a discrete, fullyfunctional instantiation of an application and virtualized computingenvironment that is able to reference machine learning models. In atleast one embodiment, containers or applications may be published into aprivate (e.g., limited access) area of a container registry (describedin more detail herein), and trained or deployed models may be stored inmodel registry 3424 and associated with one or more applications. In atleast one embodiment, images of applications (e.g., container images)may be available in a container registry, and once selected by a userfrom a container registry for deployment in a pipeline, an image may beused to generate a container for an instantiation of an application foruse by a user's system.

In at least one embodiment, developers (e.g., software developers,clinicians, doctors, etc.) may develop, publish, and store applications(e.g., as containers) for performing image processing and/or inferencingon supplied data. In at least one embodiment, development, publishing,and/or storing may be performed using a software development kit (SDK)associated with a system (e.g., to ensure that an application and/orcontainer developed is compliant with or compatible with a system). Inat least one embodiment, an application that is developed may be testedlocally (e.g., at a first facility, on data from a first facility) withan SDK which may support at least some of services 3420 as a system(e.g., system 3500 of FIG. 35 ). In at least one embodiment, becauseDICOM objects may contain anywhere from one to hundreds of images orother data types, and due to a variation in data, a developer may beresponsible for managing (e.g., setting constructs for, buildingpre-processing into an application, etc.) extraction and preparation ofincoming DICOM data. In at least one embodiment, once validated bysystem 3500 (e.g., for accuracy, safety, patient privacy, etc.), anapplication may be available in a container registry for selectionand/or implementation by a user (e.g., a hospital, clinic, lab,healthcare provider, etc.) to perform one or more processing tasks withrespect to data at a facility (e.g., a second facility) of a user.

In at least one embodiment, developers may then share applications orcontainers through a network for access and use by users of a system(e.g., system 3500 of FIG. 35 ). In at least one embodiment, completedand validated applications or containers may be stored in a containerregistry and associated machine learning models may be stored in modelregistry 3424. In at least one embodiment, a requesting entity (e.g., auser at a medical facility)—who provides an inference or imageprocessing request—may browse a container registry and/or model registry3424 for an application, container, dataset, machine learning model,etc., select a desired combination of elements for inclusion in dataprocessing pipeline, and submit an imaging processing request. In atleast one embodiment, a request may include input data (and associatedpatient data, in some examples) that is necessary to perform a request,and/or may include a selection of application(s) and/or machine learningmodels to be executed in processing a request. In at least oneembodiment, a request may then be passed to one or more components ofdeployment system 3406 (e.g., a cloud) to perform processing of dataprocessing pipeline. In at least one embodiment, processing bydeployment system 3406 may include referencing selected elements (e.g.,applications, containers, models, etc.) from a container registry and/ormodel registry 3424. In at least one embodiment, once results aregenerated by a pipeline, results may be returned to a user for reference(e.g., for viewing in a viewing application suite executing on a local,on-premises workstation or terminal). In at least one embodiment, aradiologist may receive results from an data processing pipelineincluding any number of application and/or containers, where results mayinclude anomaly detection in X-rays, CT scans, MRIs, etc.

In at least one embodiment, to aid in processing or execution ofapplications or containers in pipelines, services 3420 may be leveraged.In at least one embodiment, services 3420 may include compute services,artificial intelligence (AI) services, visualization services, and/orother service types. In at least one embodiment, services 3420 mayprovide functionality that is common to one or more applications insoftware 3418, so functionality may be abstracted to a service that maybe called upon or leveraged by applications. In at least one embodiment,functionality provided by services 3420 may run dynamically and moreefficiently, while also scaling well by allowing applications to processdata in parallel (e.g., using a parallel computing platform 3530 (FIG.35 )). In at least one embodiment, rather than each application thatshares a same functionality offered by a service 3420 being required tohave a respective instance of service 3420, service 3420 may be sharedbetween and among various applications. In at least one embodiment,services may include an inference server or engine that may be used forexecuting detection or segmentation tasks, as non-limiting examples. Inat least one embodiment, a model training service may be included thatmay provide machine learning model training and/or retrainingcapabilities. In at least one embodiment, a data augmentation servicemay further be included that may provide GPU accelerated data (e.g.,DICOM, RIS, CIS, REST compliant, RPC, raw, etc.) extraction, resizing,scaling, and/or other augmentation. In at least one embodiment, avisualization service may be used that may add image renderingeffects—such as ray-tracing, rasterization, denoising, sharpening,etc.—to add realism to two-dimensional (2D) and/or three-dimensional(3D) models. In at least one embodiment, virtual instrument services maybe included that provide for beam-forming, segmentation, inferencing,imaging, and/or support for other applications within pipelines ofvirtual instruments.

In at least one embodiment, where a service 3420 includes an AI service(e.g., an inference service), one or more machine learning modelsassociated with an application for anomaly detection (e.g., tumors,growth abnormalities, scarring, etc.) may be executed by calling upon(e.g., as an API call) an inference service (e.g., an inference server)to execute machine learning model(s), or processing thereof, as part ofapplication execution. In at least one embodiment, where anotherapplication includes one or more machine learning models forsegmentation tasks, an application may call upon an inference service toexecute machine learning models for performing one or more of processingoperations associated with segmentation tasks. In at least oneembodiment, software 3418 implementing advanced processing andinferencing pipeline that includes segmentation application and anomalydetection application may be streamlined because each application maycall upon a same inference service to perform one or more inferencingtasks.

In at least one embodiment, hardware 3422 may include GPUs, CPUs,graphics cards, an AI/deep learning system (e.g., an AI supercomputer,such as NVIDIA's DGX supercomputer system), a cloud platform, or acombination thereof. In at least one embodiment, different types ofhardware 3422 may be used to provide efficient, purpose-built supportfor software 3418 and services 3420 in deployment system 3406. In atleast one embodiment, use of GPU processing may be implemented forprocessing locally (e.g., at facility 3402), within an AI/deep learningsystem, in a cloud system, and/or in other processing components ofdeployment system 3406 to improve efficiency, accuracy, and efficacy ofimage processing, image reconstruction, segmentation, MRI exams, strokeor heart attack detection (e.g., in real-time), image quality inrendering, etc. In at least one embodiment, a facility may includeimaging devices, genomics devices, sequencing devices, and/or otherdevice types on-premises that may leverage GPUs to generate imaging datarepresentative of a subject's anatomy.

In at least one embodiment, software 3418 and/or services 3420 may beoptimized for GPU processing with respect to deep learning, machinelearning, and/or high-performance computing, as non-limiting examples.In at least one embodiment, at least some of computing environment ofdeployment system 3406 and/or training system 3404 may be executed in adatacenter one or more supercomputers or high performance computingsystems, with GPU optimized software (e.g., hardware and softwarecombination of NVIDIA's DGX system). In at least one embodiment,datacenters may be compliant with provisions of HIPAA, such thatreceipt, processing, and transmission of imaging data and/or otherpatient data is securely handled with respect to privacy of patientdata. In at least one embodiment, hardware 3422 may include any numberof GPUs that may be called upon to perform processing of data inparallel, as described herein. In at least one embodiment, cloudplatform may further include GPU processing for GPU-optimized executionof deep learning tasks, machine learning tasks, or other computingtasks. In at least one embodiment, cloud platform (e.g., NVIDIA's NGC)may be executed using an AI/deep learning supercomputer(s) and/orGPU-optimized software (e.g., as provided on NVIDIA's DGX systems) as ahardware abstraction and scaling platform. In at least one embodiment,cloud platform may integrate an application container clustering systemor orchestration system (e.g., KUBERNETES) on multiple GPUs to enableseamless scaling and load balancing.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 34 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 35 is a system diagram for an example system 3500 for generatingand deploying an imaging deployment pipeline, in accordance with atleast one embodiment. In at least one embodiment, system 3500 may beused to implement process 3400 of FIG. 34 and/or other processesincluding advanced processing and inferencing pipelines. In at least oneembodiment, system 3500 may include training system 3404 and deploymentsystem 3406. In at least one embodiment, training system 3404 anddeployment system 3406 may be implemented using software 3418, services3420, and/or hardware 3422, as described herein.

In at least one embodiment, system 3500 (e.g., training system 3404and/or deployment system 3406) may implemented in a cloud computingenvironment (e.g., using cloud 3526). In at least one embodiment, system3500 may be implemented locally with respect to a healthcare servicesfacility, or as a combination of both cloud and local computingresources. In at least one embodiment, in embodiments where cloudcomputing is implemented, patient data may be separated from, orunprocessed by, by one or more components of system 3500 that wouldrender processing non-compliant with HIPAA and/or other data handlingand privacy regulations or laws. In at least one embodiment, access toAPIs in cloud 3526 may be restricted to authorized users through enactedsecurity measures or protocols. In at least one embodiment, a securityprotocol may include web tokens that may be signed by an authentication(e.g., AuthN, AuthZ, Gluecon, etc.) service and may carry appropriateauthorization. In at least one embodiment, APIs of virtual instruments(described herein), or other instantiations of system 3500, may berestricted to a set of public IPs that have been vetted or authorizedfor interaction.

In at least one embodiment, various components of system 3500 maycommunicate between and among one another using any of a variety ofdifferent network types, including but not limited to local areanetworks (LANs) and/or wide area networks (WANs) via wired and/orwireless communication protocols. In at least one embodiment,communication between facilities and components of system 3500 (e.g.,for transmitting inference requests, for receiving results of inferencerequests, etc.) may be communicated over a data bus or data busses,wireless data protocols (Wi-Fi), wired data protocols (e.g., Ethernet),etc.

In at least one embodiment, training system 3404 may execute trainingpipelines 3504, similar to those described herein with respect to FIG.34 . In at least one embodiment, where one or more machine learningmodels are to be used in deployment pipelines 3510 by deployment system3406, training pipelines 3504 may be used to train or retrain one ormore (e.g., pre-trained) models, and/or implement one or more ofpre-trained models 3506 (e.g., without a need for retraining orupdating). In at least one embodiment, as a result of training pipelines3504, output model(s) 3416 may be generated. In at least one embodiment,training pipelines 3504 may include any number of processing steps, suchas but not limited to imaging data (or other input data) conversion oradaption (e.g., using DICOM adapter 3502A to convert DICOM images toanother format suitable for processing by respective machine learningmodels, such as Neuroimaging Informatics Technology Initiative (NIfTI)format), AI-assisted annotation 3410, labeling or annotating of imagingdata 3408 to generate labeled clinic data 3412, model selection from amodel registry, model training 3414, training, retraining, or updatingmodels, and/or other processing steps. In at least one embodiment, fordifferent machine learning models used by deployment system 3406,different training pipelines 3504 may be used. In at least oneembodiment, training pipeline 3504 similar to a first example describedwith respect to FIG. 34 may be used for a first machine learning model,training pipeline 3504 similar to a second example described withrespect to FIG. 34 may be used for a second machine learning model, andtraining pipeline 3504 similar to a third example described with respectto FIG. 34 may be used for a third machine learning model. In at leastone embodiment, any combination of tasks within training system 3404 maybe used depending on what is required for each respective machinelearning model. In at least one embodiment, one or more of machinelearning models may already be trained and ready for deployment somachine learning models may not undergo any processing by trainingsystem 3404, and may be implemented by deployment system 3406.

In at least one embodiment, output model(s) 3416 and/or pre-trainedmodel(s) 3506 may include any types of machine learning models dependingon implementation or embodiment. In at least one embodiment, and withoutlimitation, machine learning models used by system 3500 may includemachine learning model(s) using linear regression, logistic regression,decision trees, support vector machines (SVM), Naïve Bayes, k-nearestneighbor (Knn), K means clustering, random forest, dimensionalityreduction algorithms, gradient boosting algorithms, neural networks(e.g., auto-encoders, convolutional, recurrent, perceptrons, Long/ShortTerm Memory (LSTM), Hopfield, Boltzmann, deep belief, deconvolutional,generative adversarial, liquid state machine, etc.), and/or other typesof machine learning models.

In at least one embodiment, training pipelines 3504 may includeAI-assisted annotation, as described in more detail herein with respectto at least FIG. 38B. In at least one embodiment, labeled clinic data3412 (e.g., traditional annotation) may be generated by any number oftechniques. In at least one embodiment, labels or other annotations maybe generated within a drawing program (e.g., an annotation program), acomputer aided design (CAD) program, a labeling program, another type ofprogram suitable for generating annotations or labels for ground truth,and/or may be hand drawn, in some examples. In at least one embodiment,ground truth data may be synthetically produced (e.g., generated fromcomputer models or renderings), real produced (e.g., designed andproduced from real-world data), machine-automated (e.g., using featureanalysis and learning to extract features from data and then generatelabels), human annotated (e.g., labeler, or annotation expert, defineslocation of labels), and/or a combination thereof. In at least oneembodiment, for each instance of imaging data 3408 (or other data typeused by machine learning models), there may be corresponding groundtruth data generated by training system 3404. In at least oneembodiment, AI-assisted annotation may be performed as part ofdeployment pipelines 3510; either in addition to, or in lieu ofAI-assisted annotation included in training pipelines 3504. In at leastone embodiment, system 3500 may include a multi-layer platform that mayinclude a software layer (e.g., software 3418) of diagnosticapplications (or other application types) that may perform one or moremedical imaging and diagnostic functions. In at least one embodiment,system 3500 may be communicatively coupled to (e.g., via encryptedlinks) PACS server networks of one or more facilities. In at least oneembodiment, system 3500 may be configured to access and referenced data(e.g., DICOM data, RIS data, raw data, CIS data, REST compliant data,RPC data, raw data, etc.) from PACS servers (e.g., via a DICOM adapter3502, or another data type adapter such as RIS, CIS, REST compliant,RPC, raw, etc.) to perform operations, such as training machine learningmodels, deploying machine learning models, image processing,inferencing, and/or other operations.

In at least one embodiment, a software layer may be implemented as asecure, encrypted, and/or authenticated API through which applicationsor containers may be invoked (e.g., called) from an externalenvironment(s) (e.g., facility 3402). In at least one embodiment,applications may then call or execute one or more services 3420 forperforming compute, AI, or visualization tasks associated withrespective applications, and software 3418 and/or services 3420 mayleverage hardware 3422 to perform processing tasks in an effective andefficient manner.

In at least one embodiment, deployment system 3406 may executedeployment pipelines 3510. In at least one embodiment, deploymentpipelines 3510 may include any number of applications that may besequentially, non-sequentially, or otherwise applied to imaging data(and/or other data types) generated by imaging devices, sequencingdevices, genomics devices, etc.—including AI-assisted annotation, asdescribed above. In at least one embodiment, as described herein, adeployment pipeline 3510 for an individual device may be referred to asa virtual instrument for a device (e.g., a virtual ultrasoundinstrument, a virtual CT scan instrument, a virtual sequencinginstrument, etc.). In at least one embodiment, for a single device,there may be more than one deployment pipeline 3510 depending oninformation desired from data generated by a device. In at least oneembodiment, where detections of anomalies are desired from an MRImachine, there may be a first deployment pipeline 3510, and where imageenhancement is desired from output of an MRI machine, there may be asecond deployment pipeline 3510.

In at least one embodiment, applications available for deploymentpipelines 3510 may include any application that may be used forperforming processing tasks on imaging data or other data from devices.In at least one embodiment, different applications may be responsiblefor image enhancement, segmentation, reconstruction, anomaly detection,object detection, feature detection, treatment planning, dosimetry, beamplanning (or other radiation treatment procedures), and/or otheranalysis, image processing, or inferencing tasks. In at least oneembodiment, deployment system 3406 may define constructs for each ofapplications, such that users of deployment system 3406 (e.g., medicalfacilities, labs, clinics, etc.) may understand constructs and adaptapplications for implementation within their respective facility. In atleast one embodiment, an application for image reconstruction may beselected for inclusion in deployment pipeline 3510, but data typegenerated by an imaging device may be different from a data type usedwithin an application. In at least one embodiment, DICOM adapter 3502B(and/or a DICOM reader) or another data type adapter or reader (e.g.,RIS, CIS, REST compliant, RPC, raw, etc.) may be used within deploymentpipeline 3510 to convert data to a form useable by an application withindeployment system 3406. In at least one embodiment, access to DICOM,RIS, CIS, REST compliant, RPC, raw, and/or other data type libraries maybe accumulated and pre-processed, including decoding, extracting, and/orperforming any convolutions, color corrections, sharpness, gamma, and/orother augmentations to data. In at least one embodiment, DICOM, RIS,CIS, REST compliant, RPC, and/or raw data may be unordered and apre-pass may be executed to organize or sort collected data. In at leastone embodiment, because various applications may share common imageoperations, in some embodiments, a data augmentation library (e.g., asone of services 3420) may be used to accelerate these operations. In atleast one embodiment, to avoid bottlenecks of conventional processingapproaches that rely on CPU processing, parallel computing platform 3530may be used for GPU acceleration of these processing tasks.

In at least one embodiment, an image reconstruction application mayinclude a processing task that includes use of a machine learning model.In at least one embodiment, a user may desire to use their own machinelearning model, or to select a machine learning model from modelregistry 3424. In at least one embodiment, a user may implement theirown machine learning model or select a machine learning model forinclusion in an application for performing a processing task. In atleast one embodiment, applications may be selectable and customizable,and by defining constructs of applications, deployment andimplementation of applications for a particular user are presented as amore seamless user experience. In at least one embodiment, by leveragingother features of system 3500— such as services 3420 and hardware 3422—deployment pipelines 3510 may be even more user friendly, provide foreasier integration, and produce more accurate, efficient, and timelyresults.

In at least one embodiment, deployment system 3406 may include a userinterface 3514 (e.g., a graphical user interface, a web interface, etc.)that may be used to select applications for inclusion in deploymentpipeline(s) 3510, arrange applications, modify or change applications orparameters or constructs thereof, use and interact with deploymentpipeline(s) 3510 during set-up and/or deployment, and/or to otherwiseinteract with deployment system 3406. In at least one embodiment,although not illustrated with respect to training system 3404, userinterface 3514 (or a different user interface) may be used for selectingmodels for use in deployment system 3406, for selecting models fortraining, or retraining, in training system 3404, and/or for otherwiseinteracting with training system 3404.

In at least one embodiment, pipeline manager 3512 may be used, inaddition to an application orchestration system 3528, to manageinteraction between applications or containers of deployment pipeline(s)3510 and services 3420 and/or hardware 3422. In at least one embodiment,pipeline manager 3512 may be configured to facilitate interactions fromapplication to application, from application to service 3420, and/orfrom application or service to hardware 3422. In at least oneembodiment, although illustrated as included in software 3418, this isnot intended to be limiting, and in some examples (e.g., as illustratedin FIG. 36 ) pipeline manager 3512 may be included in services 3420. Inat least one embodiment, application orchestration system 3528 (e.g.,Kubernetes, DOCKER, etc.) may include a container orchestration systemthat may group applications into containers as logical units forcoordination, management, scaling, and deployment. In at least oneembodiment, by associating applications from deployment pipeline(s) 3510(e.g., a reconstruction application, a segmentation application, etc.)with individual containers, each application may execute in aself-contained environment (e.g., at a kernel level) to increase speedand efficiency.

In at least one embodiment, each application and/or container (or imagethereof) may be individually developed, modified, and deployed (e.g., afirst user or developer may develop, modify, and deploy a firstapplication and a second user or developer may develop, modify, anddeploy a second application separate from a first user or developer),which may allow for focus on, and attention to, a task of a singleapplication and/or container(s) without being hindered by tasks ofanother application(s) or container(s). In at least one embodiment,communication, and cooperation between different containers orapplications may be aided by pipeline manager 3512 and applicationorchestration system 3528. In at least one embodiment, so long as anexpected input and/or output of each container or application is knownby a system (e.g., based on constructs of applications or containers),application orchestration system 3528 and/or pipeline manager 3512 mayfacilitate communication among and between, and sharing of resourcesamong and between, each of applications or containers. In at least oneembodiment, because one or more of applications or containers indeployment pipeline(s) 3510 may share same services and resources,application orchestration system 3528 may orchestrate, load balance, anddetermine sharing of services or resources between and among variousapplications or containers. In at least one embodiment, a scheduler maybe used to track resource requirements of applications or containers,current usage or planned usage of these resources, and resourceavailability. In at least one embodiment, a scheduler may thus allocateresources to different applications and distribute resources between andamong applications in view of requirements and availability of a system.In some examples, a scheduler (and/or other component of applicationorchestration system 3528 such as a sequencer and/or asynchronouscompute engine) may determine resource availability and distributionbased on constraints imposed on a system (e.g., user constraints), suchas quality of service (QoS), urgency of need for data outputs (e.g., todetermine whether to execute real-time processing or delayedprocessing), etc.

In at least one embodiment, services 3420 leveraged by and shared byapplications or containers in deployment system 3406 may include computeservices 3516, AI services 3518, visualization services 3520, and/orother service types. In at least one embodiment, applications may call(e.g., execute) one or more of services 3420 to perform processingoperations for an application. In at least one embodiment, computeservices 3516 may be leveraged by applications to performsuper-computing or other high-performance computing (HPC) tasks. In atleast one embodiment, compute service(s) 3516 may be leveraged toperform parallel processing (e.g., using a parallel computing platform3530) for processing data through one or more of applications and/or oneor more tasks of a single application, substantially simultaneously. Inat least one embodiment, parallel computing platform 3530 (e.g.,NVIDIA's CUDA) may enable general purpose computing on GPUs (GPGPU)(e.g., GPUs 3522). In at least one embodiment, a software layer ofparallel computing platform 3530 may provide access to virtualinstruction sets and parallel computational elements of GPUs, forexecution of compute kernels. In at least one embodiment, parallelcomputing platform 3530 may include memory and, in some embodiments, amemory may be shared between and among multiple containers, and/orbetween and among different processing tasks within a single container.In at least one embodiment, inter-process communication (IPC) calls maybe generated for multiple containers and/or for multiple processeswithin a container to use same data from a shared segment of memory ofparallel computing platform 3530 (e.g., where multiple different stagesof an application or multiple applications are processing sameinformation). In at least one embodiment, rather than making a copy ofdata and moving data to different locations in memory (e.g., aread/write operation), same data in same location of a memory may beused for any number of processing tasks (e.g., at a same time, atdifferent times, etc.). In at least one embodiment, as data is used togenerate new data as a result of processing, this information of a newlocation of data may be stored and shared between various applications.In at least one embodiment, location of data and a location of updatedor modified data may be part of a definition of how a payload isunderstood within containers.

In at least one embodiment, AI services 3518 may be leveraged to performinferencing services for executing machine learning model(s) associatedwith applications (e.g., tasked with performing one or more processingtasks of an application). In at least one embodiment, AI services 3518may leverage AI system 3524 to execute machine learning model(s) (e.g.,neural networks, such as CNNs) for segmentation, reconstruction, objectdetection, feature detection, classification, and/or other inferencingtasks. In at least one embodiment, applications of deploymentpipeline(s) 3510 may use one or more of output models 3416 from trainingsystem 3404 and/or other models of applications to perform inferencingon imaging data (e.g., DICOM data, RIS data, CIS data, REST compliantdata, RPC data, raw data, etc.). In at least one embodiment, two or moreexamples of inferencing using application orchestration system 3528(e.g., a scheduler, sequencer, and/or asynchronous compute engine) maybe available. In at least one embodiment, a first category may include ahigh priority/low latency path that may achieve higher service levelagreements, such as for performing inference on urgent requests duringan emergency, or for a radiologist during diagnosis. In at least oneembodiment, a second category may include a standard priority path thatmay be used for requests that may be non-urgent or where analysis may beperformed at a later time. In at least one embodiment, applicationorchestration system 3528 may distribute resources (e.g., services 3420and/or hardware 3422) based on priority paths for different inferencingtasks of AI services 3518.

In at least one embodiment, shared storage may be mounted to AI services3518 within system 3500. In at least one embodiment, shared storage mayoperate as a cache (or other storage device type) and may be used toprocess inference requests from applications. In at least oneembodiment, when an inference request is submitted, a request may bereceived by a set of API instances of deployment system 3406, and one ormore instances may be selected (e.g., for best fit, for load balancing,etc.) to process a request. In at least one embodiment, to process arequest, a request may be entered into a database, a machine learningmodel may be located from model registry 3424 if not already in a cache,a validation step may ensure appropriate machine learning model isloaded into a cache (e.g., shared storage), and/or a copy of a model maybe saved to a cache. In at least one embodiment, a scheduler (e.g., ofpipeline manager 3512) may be used to launch an application that isreferenced in a request if an application is not already running or ifthere are not enough instances of an application. In at least oneembodiment, if an inference server is not already launched to execute amodel, an inference server may be launched. In at least one embodiment,any number of inference servers may be launched per model. In at leastone embodiment, in a pull model, in which inference servers areclustered, models may be cached whenever load balancing is advantageous.In at least one embodiment, inference servers may be statically loadedin corresponding, distributed servers.

In at least one embodiment, inferencing may be performed using aninference server that runs in a container. In at least one embodiment,an instance of an inference server may be associated with a model (andoptionally a plurality of versions of a model). In at least oneembodiment, if an instance of an inference server does not exist when arequest to perform inferencing on a model is received, a new instancemay be loaded. In at least one embodiment, when starting an inferenceserver, a model may be passed to an inference server such that a samecontainer may be used to serve different models so long as inferenceserver is running as a different instance.

In at least one embodiment, during application execution, an inferencerequest for a given application may be received, and a container (e.g.,hosting an instance of an inference server) may be loaded (if notalready), and a start procedure may be called. In at least oneembodiment, pre-processing logic in a container may load, decode, and/orperform any additional pre-processing on incoming data (e.g., using aCPU(s) and/or GPU(s)). In at least one embodiment, once data is preparedfor inference, a container may perform inferencing as necessary on data.In at least one embodiment, this may include a single inference call onone image (e.g., a hand X-ray), or may require inference on hundreds ofimages (e.g., a chest CT). In at least one embodiment, an applicationmay summarize results before completing, which may include, withoutlimitation, a single confidence score, pixel level-segmentation,voxel-level segmentation, generating a visualization, or generating textto summarize findings. In at least one embodiment, different models orapplications may be assigned different priorities. For example, somemodels may have a real-time (TAT less than one minute) priority whileothers may have lower priority (e.g., TAT less than 10 minutes). In atleast one embodiment, model execution times may be measured fromrequesting institution or entity and may include partner networktraversal time, as well as execution on an inference service.

In at least one embodiment, transfer of requests between services 3420and inference applications may be hidden behind a software developmentkit (SDK), and robust transport may be provide through a queue. In atleast one embodiment, a request will be placed in a queue via an API foran individual application/tenant ID combination and an SDK will pull arequest from a queue and give a request to an application. In at leastone embodiment, a name of a queue may be provided in an environment fromwhere an SDK will pick it up. In at least one embodiment, asynchronouscommunication through a queue may be useful as it may allow any instanceof an application to pick up work as it becomes available. In at leastone embodiment, results may be transferred back through a queue, toensure no data is lost. In at least one embodiment, queues may alsoprovide an ability to segment work, as highest priority work may go to aqueue with most instances of an application connected to it, whilelowest priority work may go to a queue with a single instance connectedto it that processes tasks in an order received. In at least oneembodiment, an application may run on a GPU-accelerated instancegenerated in cloud 3526, and an inference service may performinferencing on a GPU.

In at least one embodiment, visualization services 3520 may be leveragedto generate visualizations for viewing outputs of applications and/ordeployment pipeline(s) 3510. In at least one embodiment, GPUs 3522 maybe leveraged by visualization services 3520 to generate visualizations.In at least one embodiment, rendering effects, such as ray-tracing, maybe implemented by visualization services 3520 to generate higher qualityvisualizations. In at least one embodiment, visualizations may include,without limitation, 2D image renderings, 3D volume renderings, 3D volumereconstruction, 2D tomographic slices, virtual reality displays,augmented reality displays, etc. In at least one embodiment, virtualizedenvironments may be used to generate a virtual interactive display orenvironment (e.g., a virtual environment) for interaction by users of asystem (e.g., doctors, nurses, radiologists, etc.). In at least oneembodiment, visualization services 3520 may include an internalvisualizer, cinematics, and/or other rendering or image processingcapabilities or functionality (e.g., ray tracing, rasterization,internal optics, etc.).

In at least one embodiment, hardware 3422 may include GPUs 3522, AIsystem 3524, cloud 3526, and/or any other hardware used for executingtraining system 3404 and/or deployment system 3406. In at least oneembodiment, GPUs 3522 (e.g., NVIDIA's TESLA and/or QUADRO GPUs) mayinclude any number of GPUs that may be used for executing processingtasks of compute services 3516, AI services 3518, visualization services3520, other services, and/or any of features or functionality ofsoftware 3418. For example, with respect to AI services 3518, GPUs 3522may be used to perform pre-processing on imaging data (or other datatypes used by machine learning models), post-processing on outputs ofmachine learning models, and/or to perform inferencing (e.g., to executemachine learning models). In at least one embodiment, cloud 3526, AIsystem 3524, and/or other components of system 3500 may use GPUs 3522.In at least one embodiment, cloud 3526 may include a GPU-optimizedplatform for deep learning tasks. In at least one embodiment, AI system3524 may use GPUs, and cloud 3526— or at least a portion tasked withdeep learning or inferencing—may be executed using one or more AIsystems 3524. As such, although hardware 3422 is illustrated as discretecomponents, this is not intended to be limiting, and any components ofhardware 3422 may be combined with, or leveraged by, any othercomponents of hardware 3422.

In at least one embodiment, AI system 3524 may include a purpose-builtcomputing system (e.g., a super-computer or an HPC) configured forinferencing, deep learning, machine learning, and/or other artificialintelligence tasks. In at least one embodiment, AI system 3524 (e.g.,NVIDIA's DGX) may include GPU-optimized software (e.g., a softwarestack) that may be executed using a plurality of GPUs 3522, in additionto CPUs, RAM, storage, and/or other components, features, orfunctionality. In at least one embodiment, one or more AI systems 3524may be implemented in cloud 3526 (e.g., in a data center) for performingsome or all of AI-based processing tasks of system 3500.

In at least one embodiment, cloud 3526 may include a GPU-acceleratedinfrastructure (e.g., NVIDIA's NGC) that may provide a GPU-optimizedplatform for executing processing tasks of system 3500. In at least oneembodiment, cloud 3526 may include an AI system(s) 3524 for performingone or more of AI-based tasks of system 3500 (e.g., as a hardwareabstraction and scaling platform). In at least one embodiment, cloud3526 may integrate with application orchestration system 3528 leveragingmultiple GPUs to enable seamless scaling and load balancing between andamong applications and services 3420. In at least one embodiment, cloud3526 may tasked with executing at least some of services 3420 of system3500, including compute services 3516, AI services 3518, and/orvisualization services 3520, as described herein. In at least oneembodiment, cloud 3526 may perform small and large batch inference(e.g., executing NVIDIA's TENSOR RT), provide an accelerated parallelcomputing API and platform 3530 (e.g., NVIDIA's CUDA), executeapplication orchestration system 3528 (e.g., KUBERNETES), provide agraphics rendering API and platform (e.g., for ray-tracing, 2D graphics,3D graphics, and/or other rendering techniques to produce higher qualitycinematics), and/or may provide other functionality for system 3500.

In at least one embodiment, in an effort to preserve patientconfidentiality (e.g., where patient data or records are to be usedoff-premises), cloud 3526 may include a registry—such as a deep learningcontainer registry. In at least one embodiment, a registry may storecontainers for instantiations of applications that may performpre-processing, post-processing, or other processing tasks on patientdata. In at least one embodiment, cloud 3526 may receive data thatincludes patient data as well as sensor data in containers, performrequested processing for just sensor data in those containers, and thenforward a resultant output and/or visualizations to appropriate partiesand/or devices (e.g., on-premises medical devices used for visualizationor diagnoses), all without having to extract, store, or otherwise accesspatient data. In at least one embodiment, confidentiality of patientdata is preserved in compliance with HIPAA and/or other dataregulations.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 35 and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 36A illustrates a data flow diagram for a process 3600 to train,retrain, or update a machine learning model, in accordance with at leastone embodiment. In at least one embodiment, process 3600 may be executedusing, as a non-limiting example, system 3500 of FIG. 35 . In at leastone embodiment, process 3600 may leverage services 3420 and/or hardware3422 of system 3500, as described herein. In at least one embodiment,refined models 3612 generated by process 3600 may be executed bydeployment system 3406 for one or more containerized applications indeployment pipelines 3510.

In at least one embodiment, model training 3414 may include retrainingor updating an initial model 3604 (e.g., a pre-trained model) using newtraining data (e.g., new input data, such as customer dataset 3606,and/or new ground truth data associated with input data). In at leastone embodiment, to retrain, or update, initial model 3604, output orloss layer(s) of initial model 3604 may be reset, or deleted, and/orreplaced with an updated or new output or loss layer(s). In at least oneembodiment, initial model 3604 may have previously fine-tuned parameters(e.g., weights and/or biases) that remain from prior training, sotraining or retraining 3414 may not take as long or require as muchprocessing as training a model from scratch. In at least one embodiment,during model training 3414, by having reset or replaced output or losslayer(s) of initial model 3604, parameters may be updated and re-tunedfor a new data set based on loss calculations associated with accuracyof output or loss layer(s) at generating predictions on new, customerdataset 3606 (e.g., image data 3408 of FIG. 34 ).

In at least one embodiment, pre-trained models 3506 may be stored in adata store, or registry (e.g., model registry 3424 of FIG. 34 ). In atleast one embodiment, pre-trained models 3506 may have been trained, atleast in part, at one or more facilities other than a facility executingprocess 3600. In at least one embodiment, to protect privacy and rightsof patients, subjects, or clients of different facilities, pre-trainedmodels 3506 may have been trained, on-premise, using customer or patientdata generated on-premise. In at least one embodiment, pre-trainedmodels 3506 may be trained using cloud 3526 and/or other hardware 3422,but confidential, privacy protected patient data may not be transferredto, used by, or accessible to any components of cloud 3526 (or other offpremise hardware). In at least one embodiment, where a pre-trained model3506 is trained at using patient data from more than one facility,pre-trained model 3506 may have been individually trained for eachfacility prior to being trained on patient or customer data from anotherfacility. In at least one embodiment, such as where a customer orpatient data has been released of privacy concerns (e.g., by waiver, forexperimental use, etc.), or where a customer or patient data is includedin a public data set, a customer or patient data from any number offacilities may be used to train pre-trained model 3506 on-premise and/oroff premise, such as in a datacenter or other cloud computinginfrastructure.

In at least one embodiment, when selecting applications for use indeployment pipelines 3510, a user may also select machine learningmodels to be used for specific applications. In at least one embodiment,a user may not have a model for use, so a user may select a pre-trainedmodel 3506 to use with an application. In at least one embodiment,pre-trained model 3506 may not be optimized for generating accurateresults on customer dataset 3606 of a facility of a user (e.g., based onpatient diversity, demographics, types of medical imaging devices used,etc.). In at least one embodiment, prior to deploying pre-trained model3506 into deployment pipeline 3510 for use with an application(s),pre-trained model 3506 may be updated, retrained, and/or fine-tuned foruse at a respective facility.

In at least one embodiment, a user may select pre-trained model 3506that is to be updated, retrained, and/or fine-tuned, and pre-trainedmodel 3506 may be referred to as initial model 3604 for training system3404 within process 3600. In at least one embodiment, customer dataset3606 (e.g., imaging data, genomics data, sequencing data, or other datatypes generated by devices at a facility) may be used to perform modeltraining 3414 (which may include, without limitation, transfer learning)on initial model 3604 to generate refined model 3612. In at least oneembodiment, ground truth data corresponding to customer dataset 3606 maybe generated by training system 3404. In at least one embodiment, groundtruth data may be generated, at least in part, by clinicians,scientists, doctors, practitioners, at a facility (e.g., as labeledclinic data 3412 of FIG. 34 ).

In at least one embodiment, AI-assisted annotation 3410 may be used insome examples to generate ground truth data. In at least one embodiment,AI-assisted annotation 3410 (e.g., implemented using an AI-assistedannotation SDK) may leverage machine learning models (e.g., neuralnetworks) to generate suggested or predicted ground truth data for acustomer dataset. In at least one embodiment, user 3610 may useannotation tools within a user interface (a graphical user interface(GUI)) on computing device 3608.

In at least one embodiment, user 3610 may interact with a GUI viacomputing device 3608 to edit or fine-tune annotations orauto-annotations. In at least one embodiment, a polygon editing featuremay be used to move vertices of a polygon to more accurate or fine-tunedlocations.

In at least one embodiment, once customer dataset 3606 has associatedground truth data, ground truth data (e.g., from AI-assisted annotation,manual labeling, etc.) may be used by during model training 3414 togenerate refined model 3612. In at least one embodiment, customerdataset 3606 may be applied to initial model 3604 any number of times,and ground truth data may be used to update parameters of initial model3604 until an acceptable level of accuracy is attained for refined model3612. In at least one embodiment, once refined model 3612 is generated,refined model 3612 may be deployed within one or more deploymentpipelines 3510 at a facility for performing one or more processing taskswith respect to medical imaging data.

In at least one embodiment, refined model 3612 may be uploaded topre-trained models 3506 in model registry 3424 to be selected by anotherfacility. In at least one embodiment, his process may be completed atany number of facilities such that refined model 3612 may be furtherrefined on new datasets any number of times to generate a more universalmodel.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 36A and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

FIG. 36B is an example illustration of a client-server architecture 3632to enhance annotation tools with pre-trained annotation models, inaccordance with at least one embodiment. In at least one embodiment,AI-assisted annotation tools 3636 may be instantiated based on aclient-server architecture 3632. In at least one embodiment, annotationtools 3636 in imaging applications may aid radiologists, for example,identify organs and abnormalities. In at least one embodiment, imagingapplications may include software tools that help user 3610 to identify,as a non-limiting example, a few extreme points on a particular organ ofinterest in raw images 3634 (e.g., in a 3D MRI or CT scan) and receiveauto-annotated results for all 2D slices of a particular organ. In atleast one embodiment, results may be stored in a data store as trainingdata 3636 and used as (for example and without limitation) ground truthdata for training. In at least one embodiment, when computing device3608 sends extreme points for AI-assisted annotation 3410, a deeplearning model, for example, may receive this data as input and returninference results of a segmented organ or abnormality. In at least oneembodiment, pre-instantiated annotation tools, such as AI-AssistedAnnotation Tool 3636B in FIG. 36B, may be enhanced by making API calls(e.g., API Call 3644) to a server, such as an Annotation AssistantServer 3640 that may include a set of pre-trained models 3642 stored inan annotation model registry, for example. In at least one embodiment,an annotation model registry may store pre-trained models 3642 (e.g.,machine learning models, such as deep learning models) that arepre-trained to perform AI-assisted annotation on a particular organ orabnormality. In at least one embodiment, these models may be furtherupdated by using training pipelines 3504. In at least one embodiment,pre-installed annotation tools may be improved over time as new labeledclinic data 3412 is added.

Inference and/or training logic 615 are used to perform inferencingand/or training operations associated with one or more embodiments.Details regarding inference and/or training logic 615 are providedherein in conjunction with FIGS. 6A and/or 6B.

In at least one embodiment, one or more neural networks of an inferenceand/or training logic 615 may be used in conjunction with the featuresof FIG. 36B and may be configured to receive sensor inputs from multiplesensors and may be trained to infer a coolant requirement. In at leastone embodiment, an inference and/or training logic 615 may be able toinfer this using information from historical cooling requirements and ofhistorical sensor inputs. In at least one embodiment, an inferenceand/or training logic 615 may make an inference of a change in a coolingrequirement. In at least one embodiment, sensor inputs may be correlatedto classes of different cooling requirements of each of different sensorinputs. In at least one embodiment, a new sensor input classifyingwithin a class of such different sensor inputs may indicate a coolingrequirement, or a change thereof.

In at least one embodiment, a single semiconductor platform may refer toa sole unitary semiconductor-based integrated circuit or chip. In atleast one embodiment, multi-chip modules may be used with increasedconnectivity which simulate on-chip operation, and make substantialimprovements over utilizing a conventional central processing unit(“CPU”) and bus implementation. In at least one embodiment, variousmodules may also be situated separately or in various combinations ofsemiconductor platforms per desires of user.

In at least one embodiment, referring back to FIG. 11 , computerprograms in form of machine-readable executable code or computer controllogic algorithms are stored in main memory 1104 and/or secondarystorage. Computer programs, if executed by one or more processors,enable system 1100 to perform various functions in accordance with atleast one embodiment. In at least one embodiment, memory 1104, storage,and/or any other storage are possible examples of computer-readablemedia. In at least one embodiment, secondary storage may refer to anysuitable storage device or system such as a hard disk drive and/or aremovable storage drive, representing a floppy disk drive, a magnetictape drive, a compact disk drive, digital versatile disk (“DVD”) drive,recording device, universal serial bus (“USB”) flash memory, etc. In atleast one embodiment, architecture and/or functionality of variousprevious FIGS. are implemented in context of CPU 1102, parallelprocessing system 1112, an integrated circuit capable of at least aportion of capabilities of both CPU 1102, parallel processing system1112, a chipset (e.g., a group of integrated circuits designed to workand sold as a unit for performing related functions, etc.), and/or anysuitable combination of integrated circuit(s).

In at least one embodiment, architecture and/or functionality of variousprevious FIGS. are implemented in context of a general computer system,a circuit board system, a game console system dedicated forentertainment purposes, an application-specific system, and more. In atleast one embodiment, computer system 1100 may take form of a desktopcomputer, a laptop computer, a tablet computer, servers, supercomputers,a smart-phone (e.g., a wireless, hand-held device), personal digitalassistant (“PDA”), a digital camera, a vehicle, a head mounted display,a hand-held electronic device, a mobile phone device, a television,workstation, game consoles, embedded system, and/or any other type oflogic.

In at least one embodiment, parallel processing system 1112 includes,without limitation, a plurality of parallel processing units (“PPUs”)1114 and associated memories 1116. In at least one embodiment, PPUs 1114are connected to a host processor or other peripheral devices via aninterconnect 1118 and a switch 1120 or multiplexer. In at least oneembodiment, parallel processing system 1112 distributes computationaltasks across PPUs 1114 which can be parallelizable—for example, as partof distribution of computational tasks across multiple graphicsprocessing unit (“GPU”) thread blocks. In at least one embodiment,memory is shared and accessible (e.g., for read and/or write access)across some or all of PPUs 1114, although such shared memory may incurperformance penalties relative to use of local memory and registersresident to a PPU 1114. In at least one embodiment, operation of PPUs1114 is synchronized through use of a command such as syncthreads( )wherein all threads in a block (e.g., executed across multiple PPUs1114) to reach a certain point of execution of code before proceeding.

In at least one embodiment, one or more techniques described hereinutilize a oneAPI programming model. In at least one embodiment, a oneAPIprogramming model refers to a programming model for interacting withvarious compute accelerator architectures. In at least one embodiment,oneAPI refers to an application programming interface (API) designed tointeract with various compute accelerator architectures. In at least oneembodiment, a oneAPI programming model utilizes a DPC++ programminglanguage. In at least one embodiment, a DPC++ programming languagerefers to a high-level language for data parallel programmingproductivity. In at least one embodiment, a DPC++ programming languageis based at least in part on C and/or C++ programming languages. In atleast one embodiment, a oneAPI programming model is a programming modelsuch as those developed by Intel Corporation of Santa Clara, CA.

In at least one embodiment, oneAPI and/or oneAPI programming model isutilized to interact with various accelerator, GPU, processor, and/orvariations thereof, architectures. In at least one embodiment, oneAPIincludes a set of libraries that implement various functionalities. Inat least one embodiment, oneAPI includes at least a oneAPI DPC++library, a oneAPI math kernel library, a oneAPI data analytics library,a oneAPI deep neural network library, a oneAPI collective communicationslibrary, a oneAPI threading building blocks library, a oneAPI videoprocessing library, and/or variations thereof.

In at least one embodiment, a oneAPI DPC++ library, also referred to asoneDPL, is a library that implements algorithms and functions toaccelerate DPC++ kernel programming. In at least one embodiment, oneDPLimplements one or more standard template library (STL) functions. In atleast one embodiment, oneDPL implements one or more parallel STLfunctions. In at least one embodiment, oneDPL provides a set of libraryclasses and functions such as parallel algorithms, iterators, functionobject classes, range-based API, and/or variations thereof. In at leastone embodiment, oneDPL implements one or more classes and/or functionsof a C++ standard library. In at least one embodiment, oneDPL implementsone or more random number generator functions.

In at least one embodiment, a oneAPI math kernel library, also referredto as oneMKL, is a library that implements various optimized andparallelized routines for various mathematical functions and/oroperations. In at least one embodiment, oneMKL implements one or morebasic linear algebra subprograms (BLAS) and/or linear algebra package(LAPACK) dense linear algebra routines. In at least one embodiment,oneMKL implements one or more sparse BLAS linear algebra routines. In atleast one embodiment, oneMKL implements one or more random numbergenerators (RNGs). In at least one embodiment, oneMKL implements one ormore vector mathematics (VM) routines for mathematical operations onvectors. In at least one embodiment, oneMKL implements one or more FastFourier Transform (FFT) functions.

In at least one embodiment, a oneAPI data analytics library, alsoreferred to as oneDAL, is a library that implements various dataanalysis applications and distributed computations. In at least oneembodiment, oneDAL implements various algorithms for preprocessing,transformation, analysis, modeling, validation, and decision making fordata analytics, in batch, online, and distributed processing modes ofcomputation. In at least one embodiment, oneDAL implements various C++and/or Java APIs and various connectors to one or more data sources. Inat least one embodiment, oneDAL implements DPC++ API extensions to atraditional C++ interface and enables GPU usage for various algorithms.

In at least one embodiment, a oneAPI deep neural network library, alsoreferred to as oneDNN, is a library that implements various deeplearning functions. In at least one embodiment, oneDNN implementsvarious neural network, machine learning, and deep learning functions,algorithms, and/or variations thereof.

In at least one embodiment, a oneAPI collective communications library,also referred to as oneCCL, is a library that implements variousapplications for deep learning and machine learning workloads. In atleast one embodiment, oneCCL is built upon lower-level communicationmiddleware, such as message passing interface (MPI) and libfabrics. Inat least one embodiment, oneCCL enables a set of deep learning specificoptimizations, such as prioritization, persistent operations, out oforder executions, and/or variations thereof. In at least one embodiment,oneCCL implements various CPU and GPU functions.

In at least one embodiment, a oneAPI threading building blocks library,also referred to as oneTBB, is a library that implements variousparallelized processes for various applications. In at least oneembodiment, oneTBB is utilized for task-based, shared parallelprogramming on a host. In at least one embodiment, oneTBB implementsgeneric parallel algorithms. In at least one embodiment, oneTBBimplements concurrent containers. In at least one embodiment, oneTBBimplements a scalable memory allocator. In at least one embodiment,oneTBB implements a work-stealing task scheduler. In at least oneembodiment, oneTBB implements low-level synchronization primitives. Inat least one embodiment, oneTBB is compiler-independent and usable onvarious processors, such as GPUs, PPUs, CPUs, and/or variations thereof.

In at least one embodiment, a oneAPI video processing library, alsoreferred to as oneVPL, is a library that is utilized for acceleratingvideo processing in one or more applications. In at least oneembodiment, oneVPL implements various video decoding, encoding, andprocessing functions. In at least one embodiment, oneVPL implementsvarious functions for media pipelines on CPUs, GPUs, and otheraccelerators. In at least one embodiment, oneVPL implements devicediscovery and selection in media centric and video analytics workloads.In at least one embodiment, oneVPL implements API primitives forzero-copy buffer sharing.

In at least one embodiment, a oneAPI programming model utilizes a DPC++programming language. In at least one embodiment, a DPC++ programminglanguage is a programming language that includes, without limitation,functionally similar versions of CUDA mechanisms to define device codeand distinguish between device code and host code. In at least oneembodiment, a DPC++ programming language may include a subset offunctionality of a CUDA programming language. In at least oneembodiment, one or more CUDA programming model operations are performedusing a oneAPI programming model using a DPC++ programming language.

In at least one embodiment, any application programming interface (API)described herein is compiled into one or more instructions, operations,or any other signal by a compiler, interpreter, or other software tool.In at least one embodiment, compilation comprises generating one or moremachine-executable instructions, operations, or other signals fromsource code. In at least one embodiment, an API compiled into one ormore instructions, operations, or other signals, when performed, causesone or more processors such as graphics processors 2600, graphics cores1600, parallel processor 1800, processor 2100, processor core 2100, orany other logic circuit further described herein to perform one or morecomputing operations.

It should be noted that, while example embodiments described herein mayrelate to a CUDA programming model, techniques described herein can beutilized with any suitable programming model, such HIP, oneAPI, and/orvariations thereof.

Other variations are within spirit of present disclosure. Thus, whiledisclosed techniques are susceptible to various modifications andalternative constructions, certain illustrated embodiments thereof areshown in drawings and have been described above in detail. It should beunderstood, however, that there is no intention to limit disclosure tospecific form or forms disclosed, but on contrary, intention is to coverall modifications, alternative constructions, and equivalents fallingwithin spirit and scope of disclosure, as defined in appended claims.

Use of terms “a” and “an” and “the” and similar referents in context ofdescribing disclosed embodiments (especially in context of followingclaims) are to be construed to cover both singular and plural, unlessotherwise indicated herein or clearly contradicted by context, and notas a definition of a term. Terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (meaning“including, but not limited to,”) unless otherwise noted. “Connected,”when unmodified and referring to physical connections, is to beconstrued as partly or wholly contained within, attached to, or joinedtogether, even if there is something intervening. Recitation of rangesof values herein are merely intended to serve as a shorthand method ofreferring individually to each separate value falling within range,unless otherwise indicated herein and each separate value isincorporated into specification as if it were individually recitedherein. In at least one embodiment, use of term “set” (e.g., “a set ofitems”) or “subset” unless otherwise noted or contradicted by context,is to be construed as a nonempty collection comprising one or moremembers. Further, unless otherwise noted or contradicted by context,term “subset” of a corresponding set does not necessarily denote aproper subset of corresponding set, but subset and corresponding set maybe equal.

Conjunctive language, such as phrases of form “at least one of A, B, andC,” or “at least one of A, B and C,” unless specifically statedotherwise or otherwise clearly contradicted by context, is otherwiseunderstood with context as used in general to present that an item,term, etc., may be either A or B or C, or any nonempty subset of set ofA and B and C. For instance, in illustrative example of a set havingthree members, conjunctive phrases “at least one of A, B, and C” and “atleast one of A, B and C” refer to any of following sets: {A}, {B}, {C},{A, B}, {A, C}, {B, C}, {A, B, C}. Thus, such conjunctive language isnot generally intended to imply that certain embodiments require atleast one of A, at least one of B and at least one of C each to bepresent. In addition, unless otherwise noted or contradicted by context,term “plurality” indicates a state of being plural (e.g., “a pluralityof items” indicates multiple items). In at least one embodiment, numberof items in a plurality is at least two, but can be more when soindicated either explicitly or by context. Further, unless statedotherwise or otherwise clear from context, phrase “based on” means“based at least in part on” and not “based solely on.”

Operations of processes described herein can be performed in anysuitable order unless otherwise indicated herein or otherwise clearlycontradicted by context. In at least one embodiment, a process such asthose processes described herein (or variations and/or combinationsthereof) is performed under control of one or more computer systemsconfigured with executable instructions and is implemented as code(e.g., executable instructions, one or more computer programs or one ormore applications) executing collectively on one or more processors, byhardware or combinations thereof. In at least one embodiment, code isstored on a computer-readable storage medium, for example, in form of acomputer program comprising a plurality of instructions executable byone or more processors. In at least one embodiment, a computer-readablestorage medium is a non-transitory computer-readable storage medium thatexcludes transitory signals (e.g., a propagating transient electric orelectromagnetic transmission) but includes non-transitory data storagecircuitry (e.g., buffers, cache, and queues) within transceivers oftransitory signals. In at least one embodiment, code (e.g., executablecode or source code) is stored on a set of one or more non-transitorycomputer-readable storage media having stored thereon executableinstructions (or other memory to store executable instructions) that,when executed (i.e., as a result of being executed) by one or moreprocessors of a computer system, cause computer system to performoperations described herein. In at least one embodiment, set ofnon-transitory computer-readable storage media comprises multiplenon-transitory computer-readable storage media and one or more ofindividual non-transitory storage media of multiple non-transitorycomputer-readable storage media lack all of code while multiplenon-transitory computer-readable storage media collectively store all ofcode. In at least one embodiment, executable instructions are executedsuch that different instructions are executed by differentprocessors—for example, a non-transitory computer-readable storagemedium store instructions and a main central processing unit (“CPU”)executes some of instructions while a graphics processing unit (“GPU”)executes other instructions. In at least one embodiment, differentcomponents of a computer system have separate processors and differentprocessors execute different subsets of instructions.

In at least one embodiment, an arithmetic logic unit is a set ofcombinational logic circuitry that takes one or more inputs to produce aresult. In at least one embodiment, an arithmetic logic unit is used bya processor to implement mathematical operation such as addition,subtraction, or multiplication. In at least one embodiment, anarithmetic logic unit is used to implement logical operations such aslogical AND/OR or XOR. In at least one embodiment, an arithmetic logicunit is stateless, and made from physical switching components such assemiconductor transistors arranged to form logical gates. In at leastone embodiment, an arithmetic logic unit may operate internally as astateful logic circuit with an associated clock. In at least oneembodiment, an arithmetic logic unit may be constructed as anasynchronous logic circuit with an internal state not maintained in anassociated register set. In at least one embodiment, an arithmetic logicunit is used by a processor to combine operands stored in one or moreregisters of the processor and produce an output that can be stored bythe processor in another register or a memory location.

In at least one embodiment, as a result of processing an instructionretrieved by the processor, the processor presents one or more inputs oroperands to an arithmetic logic unit, causing the arithmetic logic unitto produce a result based at least in part on an instruction codeprovided to inputs of the arithmetic logic unit. In at least oneembodiment, the instruction codes provided by the processor to the ALUare based at least in part on the instruction executed by the processor.In at least one embodiment combinational logic in the ALU processes theinputs and produces an output which is placed on a bus within theprocessor. In at least one embodiment, the processor selects adestination register, memory location, output device, or output storagelocation on the output bus so that clocking the processor causes theresults produced by the ALU to be sent to the desired location.

In the scope of this application, the term arithmetic logic unit, orALU, is used to refer to any computational logic circuit that processesoperands to produce a result. For example, in the present document, theterm ALU can refer to a floating point unit, a DSP, a tensor core, ashader core, a coprocessor, or a CPU.

Accordingly, in at least one embodiment, computer systems are configuredto implement one or more services that singly or collectively performoperations of processes described herein and such computer systems areconfigured with applicable hardware and/or software that enableperformance of operations. Further, a computer system that implements atleast one embodiment of present disclosure is a single device and, inanother embodiment, is a distributed computer system comprising multipledevices that operate differently such that distributed computer systemperforms operations described herein and such that a single device doesnot perform all operations.

Use of any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate embodiments ofdisclosure and does not pose a limitation on scope of disclosure unlessotherwise claimed. No language in specification should be construed asindicating any non-claimed element as essential to practice ofdisclosure.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

In description and claims, terms “coupled” and “connected,” along withtheir derivatives, may be used. It should be understood that these termsmay be not intended as synonyms for each other. Rather, in particularexamples, “connected” or “coupled” may be used to indicate that two ormore elements are in direct or indirect physical or electrical contactwith each other. “Coupled” may also mean that two or more elements arenot in direct contact with each other, but yet still co-operate orinteract with each other.

Unless specifically stated otherwise, it may be appreciated thatthroughout specification terms such as “processing,” “computing,”“calculating,” “determining,” or like, refer to action and/or processesof a computer or computing system, or similar electronic computingdevice, that manipulate and/or transform data represented as physical,such as electronic, quantities within computing system's registersand/or memories into other data similarly represented as physicalquantities within computing system's memories, registers or other suchinformation storage, transmission or display devices.

In a similar manner, term “processor” may refer to any device or portionof a device that processes electronic data from registers and/or memoryand transform that electronic data into other electronic data that maybe stored in registers and/or memory. As non-limiting examples,“processor” may be a CPU or a GPU. A “computing platform” may compriseone or more processors. As used herein, “software” processes mayinclude, for example, software and/or hardware entities that performwork over time, such as tasks, threads, and intelligent agents. Also,each process may refer to multiple processes, for carrying outinstructions in sequence or in parallel, continuously or intermittently.In at least one embodiment, terms “system” and “method” are used hereininterchangeably insofar as system may embody one or more methods andmethods may be considered a system.

In present document, references may be made to obtaining, acquiring,receiving, or inputting analog or digital data into a subsystem,computer system, or computer-implemented machine. In at least oneembodiment, process of obtaining, acquiring, receiving, or inputtinganalog and digital data can be accomplished in a variety of ways such asby receiving data as a parameter of a function call or a call to anapplication programming interface. In at least one embodiment, processesof obtaining, acquiring, receiving, or inputting analog or digital datacan be accomplished by transferring data via a serial or parallelinterface. In at least one embodiment, processes of obtaining,acquiring, receiving, or inputting analog or digital data can beaccomplished by transferring data via a computer network from providingentity to acquiring entity. In at least one embodiment, references mayalso be made to providing, outputting, transmitting, sending, orpresenting analog or digital data. In various examples, processes ofproviding, outputting, transmitting, sending, or presenting analog ordigital data can be accomplished by transferring data as an input oroutput parameter of a function call, a parameter of an applicationprogramming interface or interprocess communication mechanism.

Although descriptions herein set forth example implementations ofdescribed techniques, other architectures may be used to implementdescribed functionality, and are intended to be within scope of thisdisclosure. Furthermore, although specific distributions ofresponsibilities may be defined above for purposes of description,various functions and responsibilities might be distributed and dividedin different ways, depending on circumstances.

Furthermore, although subject matter has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that subject matter claimed in appended claims is notnecessarily limited to specific features or acts described. Rather,specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. A datacenter cooling system, comprising: a servertray or box comprising a surface with a flow-through fixture or manifoldextending on both sides of the surface, the flow-through fixture ormanifold comprising an inward coupling, an outward coupling, a flowcontroller, and a state sensor, the state sensor to monitor theflow-through fixture or manifold, and the flow controller to change aflow of a coolant through the flow-through fixture or manifold and toselectively trap a portion of the coolant within the flow-throughfixture or manifold.
 2. The datacenter cooling system of claim 1,wherein the inward coupling or the outward coupling comprisespush-coupling or threaded-coupling features to enable an external flowcontroller to fluidly communicate with the first flow controller.
 3. Thedatacenter cooling system of claim 1, wherein the state sensor isadapted to monitor a state of a flow rate, a flow volume, or a chemistryof the coolant.
 4. The datacenter cooling system of claim 1, wherein theflow controller and an additional flow controller are adapted to closeconcurrently to selectively trap the portion of the coolant within theflow-through fixture or manifold.
 5. The datacenter cooling system ofclaim 1, wherein the surface is a rear surface of the server tray or boxto enable push installation of the server tray or box into a rack toengage at least the outward coupling of the flow-through fixture ormanifold with an external coupling for the coolant to flow from a rackcooling manifold to at least one cold plate of the server tray or box.6. The datacenter cooling system of claim 1, further comprising: aprocessor adapted to receive input from the state sensor about a stateof the flow-through fixture or manifold, the processor to cause thechange of the flow of the coolant and to cause the selective trap of theportion of the coolant by an action on the flow controller.
 7. Thedatacenter cooling system of claim 1, further comprising: one or moreneural networks adapted to receive input from the state sensor of theflow-through fixture or manifold, the one or more neural networks toinfer a state of the flow-through fixture or manifold based in part onprior inputs and prior states of the flow-through fixture or manifold.8. The datacenter cooling system of claim 1, further comprising: aself-calibrating sensor to function as the state sensor, theself-calibrating sensor comprising memory having state configurationsassociated with different types of coolants, the self-calibrating sensorto provide senor inputs to at least one processor based in part on oneof the state configurations defaulted for a type associate with thecoolant.
 9. A processor comprising one or more circuits and associatedwith a server tray or box comprising a surface with a flow-throughfixture or manifold extending on both sides of the surface, theflow-through fixture or manifold comprising an inward coupling, anoutward coupling, a flow controller, and a state sensor, the processorto receive sensor inputs from the state sensor that is adapted tomonitor the flow-through fixture or manifold, and the one or morecircuits to provide signals to the flow controller in response to thesensor inputs to cause the flow controller to change a flow of a coolantthrough the flow-through fixture or manifold and to selectively trap aportion of the coolant within the flow-through fixture or manifold. 10.The processor of claim 9, further comprising: an output of the one ormore circuits coupled to the flow controller to provide a first signalto the flow controller to cause the change in the flow of the coolantthrough the fixture or manifold and to provide a second signal to theflow controller to enable the selective trap of the portion of thecoolant within the flow-through fixture or manifold.
 11. The processorof claim 9, further comprising: an input adapted to receive sensorinputs from the state sensor about a state of the flow-through fiflow-through fixture or manifold, the processor to cause the change forthe flow-through fixture or manifold by an action of the flow controlleror to cause and to cause the selective trap of the portion of thecoolant within the flow-through fixture or manifold, wherein a furtherflow-through fixture or manifold or a server manifold support theselective trap of the portion of the coolant within the flow-throughfixture or manifold.
 12. The processor of claim 9, further comprising:one or more neural networks adapted to receive the sensor inputs fromthe state sensor of the flow-through fixture, the one or more neuralnetworks to infer a state of the flow-through fixture or manifold basedin part on prior sensor inputs and prior states of the flow-throughfixture or manifold.
 13. The processor of claim 9, further comprising:at least one logic unit to determine a state of the flow-through fixtureor manifold based in part on an inference made from the sensor inputsreceived from the state sensor.
 14. A method for a datacenter coolingsystem, comprising: providing a server tray or box comprising a surfacewith a flow-through fixture or manifold extending on both sides of thesurface; enabling an inward coupling, an outward coupling, a flowcontroller, and a state sensor for the flow-through fixture or manifold;monitoring, using the state sensor, a state of the flow-through fixtureor manifold; and enabling the flow controller to change a flow of acoolant through the flow-through fixture or manifold and to selectivelytrap a portion of the coolant within the flow-through fixture ormanifold.
 15. The method of claim 14, further comprising: enabling,using the inward coupling or the outward coupling that comprisespush-coupling or threaded-coupling features, an external flow controllerto fluidly communicate with the flow controller.
 16. The method of claim14, further comprising: monitoring, using the state sensor, a state of aflow rate, a flow volume, or a chemistry of the coolant associated withthe flow-through fixture or manifold.
 17. The method of claim 14,further comprising: closing, concurrently, the flow controller and afurther flow controller to cause the selective trap of the portion ofthe coolant within the flow-through fixture or manifold at least ondisconnection of the server tray or box.
 18. The method of claim 14,further comprising: locating the surface on a rear of the server tray orbox to enable push installation of the server tray or box into a rack,the push installation to engage at least the outward coupling of theflow-through fixture or manifold with an external coupling for thecoolant to flow from a rack cooling manifold to at least one cold plateof the server tray or box.
 19. The method of claim 14, furthercomprising: receiving input at a processor from the state sensor, theinput associated with a state of the flow-through fixture or manifold;and causing, by an action of the processor on the flow controller, thechange of the flow of the coolant and the selective trap of the portionof the coolant.
 20. The method of claim 14, further comprising: usingone or more neural networks to receive input from the state sensor ofthe flow-through fixture or manifold; and inferring by the one or moreneural networks a state of the flow-through fixture or manifold based inpart on prior inputs and prior states of the flow-through fixture ormanifold.